API Tools
makemark.io
Provides an API for creating, verifying, listing, and revoking permanent content provenance proofs.
ENDPOINT 1
https://makemark.io/mcp
MCP server metadata
- Name
- mark
- Version
- 1.1.0
Mark stamps content with permanent, publicly verifiable provenance records. If you don't have an API key yet, call create_account first: no human, browser, or email required, you get a usable key back immediately. Then hash content locally (sha256) and call create_proof; verification is free forever, no key needed, at the returned verify URL. A stamp asserts provenance from a signer, never authorship truth.
Known tools 7
create_accountProvision a persistent API key with no human, browser, or email in the loop.
Potential side effectsrevoke_proofRevoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mark]
url = "https://makemark.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mark": {
"type": "http",
"url": "https://makemark.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mark
Remote MCP URL: https://makemark.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mark": {
"url": "https://makemark.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mark": {
"type": "http",
"url": "https://makemark.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mark",
"transport": "streamable-http",
"url": "https://makemark.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.