Other · Remote MCP server
Source Claim Proof
Verify whether a supplied public source currently supports one atomic factual claim.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.workers.mattskowronis.source-claim-proof/verify-source-claim- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- dev.workers.mattskowronis.source-claim-proof
- Namespace
- Namespace verified by the MCP Registry via the domain source-claim-proof.mattskowronis.workers.dev or a parent domain of it · how
- Website
- source-claim-proof.mattskowronis.workers.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://source-claim-proof.mattskowronis.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- source-claim-proof 1.0.0 · protocol 2025-06-18
- Tools discovered
- 1:
verify_source_claim - Checked on
- 2026-10-05
How to connect Source Claim Proof
Source Claim Proof is a remote MCP server: there is nothing to install. Its endpoint is https://source-claim-proof.mattskowronis.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| SoundcheckStaff live events: gigs, crew, setlists, call lists, ingest. Hosted MCP with OAuth. | Remote · HTTPLive check: sign-in required |
| SoundCreation Catalog52,000 musical instruments: prices, deals, bundles, open-box, alternatives, accessories, guides. | Remote · HTTPLive check: ✓ handshake |
| SoundGTMAI-native PRM: track partner pipeline, deals, and commissions, and manage partner outreach. | Remote · HTTPLive check: sign-in required |
| SoundingSounding checks proposed decisions and returns structured proceed, revise, or pause assessments. | Remote · HTTPLive check: sign-in required |
| Source PartsElectronic component sourcing, BOM management, and PCB design workflows. | Remote & Local · HTTP, stdioLive check: sign-in required |
| SOURCE/80 DiscoveryRead SOURCE/80 continuity status and invite-gated encrypted handoff contracts. | Remote · HTTPLive check: ✓ handshake |
| SourcerightReference verification MCP server for CSL bibliographies, evidence, and audited writes. | Local · stdio |
| SourceyFind and compare startup credits and deals with eligibility checks and exact evidence. | Remote · HTTPLive check: ✓ handshake |