Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Rotwang9000/seneschal-data-apiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/rotwang9000/seneschal-data-api/seneschal-data)<a href="https://agentmods.dev/mcp/rotwang9000/seneschal-data-api/seneschal-data"><img src="https://agentmods.dev/badge/mcp/rotwang9000/seneschal-data-api/seneschal-data/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/rotwang9000/seneschal-data-api/seneschal-data"><img src="https://agentmods.dev/badge/mcp/rotwang9000/seneschal-data-api/seneschal-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seneschal-data scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"seneschal-data": {
"url": "https://mcp.seneschal.space/",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A bc6ceaac7a1e
seneschal-data is an MCP server published in the GitHub repository Rotwang9000/seneschal-data-api (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
x402-list-mcp
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume. Runs locally from the x402-list-mcp npm package. Needs 2 environment variables to run.
suwappu
Cross-chain DEX for AI agents. Swap tokens across 7+ chains. Runs locally from the @suwappu/mcp-server npm package. Needs 1 environment variable to run.
madeonsol
Solana KOL trading intelligence & deployer analytics via x402 micropayments or API key. Runs locally from the mcp-server-madeonsol npm package.
nano-pay
Feeless x402 micropayments for AI agents — self-custodied XNO wallet, pay-per-call client, merchant server with railHint, faucet, and MCP server. Runs locally from the feeless402 Python package.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
fiatdock
A marketplace where AI agents discover MCP services and buy them from other agents per call in USDC via x402, auto-paid from your wallet — plus a non-custodial USDC-to-bank cash-out (licensed provider), first-party Base chain data and token safety. Runs locally from the fiatdock-mcp npm package. Needs 3 environment…