Developer · Remote MCP server
Provenance
Stamp or notarize data into a public witnessed transparency log. Proves timing, not truth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.MarkovianProtocol/provenance- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- MarkovianProtocol (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/MarkovianProtocol) · how
- Repository
- github.com/MarkovianProtocol/markovian-protocol
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.markovianprotocol.com/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
- markovian 0.2.0 · protocol 2025-06-18
- Tools discovered
- 4:
markovian_notarize,markovian_stamp,markovian_verify,markovian_trace - Checked on
- 2026-10-05
How to connect Provenance
Provenance is a remote MCP server: there is nothing to install. Its endpoint is https://api.markovianprotocol.com/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 developer servers
| Server | Runs |
|---|---|
| Protectwith KbAI-security knowledge as MCP: standards-mapped tools (OWASP, NIST, MITRE) for AI agents. | Remote · HTTPLive check: ✗ no handshake |
| Proton Drive CLI MCPManage Proton Drive from MCP clients through Proton's official CLI without exposing credentials. | Local · stdio |
| Provar MCP ServerProvar MCP: AI-powered Salesforce test automation. Generate, validate, migrate, and run tests. | Local · stdio |
| Provena Agent MemorySelf-hosted MCP memory for AI agents: persistent context with evidence-backed claims. | Local · stdio |
| ProvenToolsRead-only ProvenTools business ideas, evidence, build prompts, and validation reports. | Local · stdio |
| ProvidersVerified cloud storage provider facts: prices, storage, encryption. Dated and source-cited. | Remote · HTTPLive check: ✓ handshake |
| Provision StackOutcome-based infrastructure for agents - verified AWS deployments, metered billing. | Remote · HTTPLive check: ✗ no handshake |
| ProWebStoreAI-operated knowledge-graph CMS for business websites: entities, pages, blocks, media, domains. | Remote · HTTPLive check: sign-in required |