xytara MCP Executor
Pay-per-call MCP tools and signed on-chain attestations: 20 free/day, then x402 or a spend key.
Description from the maker (original English)
Stamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"otskit": {
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Run this in your terminal
claude mcp add otskit -- npx -y @otskit/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"otskit": {
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"otskit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The publisher (AlexAlves87) is not the repo owner (OTSkit); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: xytara MCP Executor, FairAgent, A2A Gateway — Base Token Guard & x402 Settlement
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Pay-per-call MCP tools and signed on-chain attestations: 20 free/day, then x402 or a spend key.
Live state and unsigned mint/claim tx builder for FairAgent AI-agent NFTs on BNB Chain.
Pre-trade Base token risk verdicts, EVM route simulation and code audits, paid per call over x402.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
OpenTimestamps MCP server - stamp, upgrade, and verify Bitcoin timestamps via AI agents.
Exposes a set of tools to any MCP-compatible agent so it can timestamp documents, monitor confirmation status, and verify proofs against the Bitcoin blockchain - all from a conversation.
This is an independent implementation of the OpenTimestamps protocol. It is not affiliated with, endorsed by, or maintained by the OpenTimestamps project.
Note on confirmation times: After stamping, a proof is
pendinguntil Bitcoin confirms it. Confirmations typically arrive within ~60 minutes, but can take several hours during network congestion. Useots-mcp watchorupgrade_timestampto monitor. A pending proof is not a failed proof.
npm install -g @otskit/mcp
ots-mcp setup claude # Claude Desktop
ots-mcp setup claude-code # Claude Code CLI ots-mcp setup codex # Codex CLI
Each command writes the MCP entry into the agent's config file, makes a .bak backup if the file already exists, and skips if ots-mcp is already configured. Restart the agent afterwards to apply the changes.
| Command | Description | ||
|---|---|---|---|
ots-mcp serve | Start the MCP server (stdio transport) | ||
ots-mcp stamp | Stamp a SHA-256 hash against Bitcoin calendars | ||
ots-mcp upgrade | Check if a pending stamp has been confirmed | ||
ots-mcp verify | Verify a stamp against Bitcoin | ||
ots-mcp list [status] | List stamps (pending / confirmed / failed) | ||
ots-mcp watch [minutes] | Monitor pending stamps and attempt due upgrades (default: 30 min, minimum: 15 min) | ||
ots-mcp check-pending | Run one upgrade pass over all pending stamps | ||
| `ots-mcp scheduler install\ | remove\ | status` | Manage OS-level scheduler for auto-upgrades |
ots-mcp backup [dest] | Backup the SQLite database | ||
ots-mcp setup | Configure MCP for an agent |
| Tool | Description |
|---|---|
create_timestamp | Stamp a SHA-256 hash against 4 public OTS calendars |
upgrade_timestamp | Check if a pending stamp has been confirmed in Bitcoin |
verify_timestamp | Verify a stamp - proves hash existed before a given Bitcoin block |
verify_external_proof | Verify a whitelisted local file against its external .ots proof, without changing the local stamp store |
inspect_timestamp | Inspect a stored proof file without network calls |
list_pending | List stamps with status, retry count, and filters |
watch | Open a terminal window monitoring pending stamps and attempting due upgrades |
hash_file | Compute the SHA-256 of a local file and return it as a 64-char hex string (no network calls) |
stamp_file | Compute SHA-256 of a local file and stamp it on Bitcoin in one step |
All data is stored in ~/.ots-mcp/:
~/.ots-mcp/
ots-mcp.db # SQLite database (stamps, proof files) config.json # Optional config overrides ots-mcp.log # Log file
Create ~/.ots-mcp/config.json to override defaults:
{
"stamp_enabled": true, "scheduler_interval_minutes": 30, "retry_max_attempts": 20, "calendar_timeout_ms": 10000, "calendars": [ "https://alice.btc.calendar.opentimestamps.org", "https://bob.btc.calendar.opentimestamps.org", "https://finney.calendar.eternitywall.com", "https://btc.calendar.catallaxy.com" ] }
npm run build # production build
npm run dev # watch mode npm test # run tests
@otskit/client - OTS calendar client (brings in @otskit/core, the protocol engine)@modelcontextprotocol/sdk - MCP SDKnode-sqlite3-wasm - local database (pure WASM, no native compilation)Requires Node.js >= 20.