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/shaqmughal/seekstoneWrote 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/shaqmughal/seekstone/seekstone)<a href="https://agentmods.dev/mcp/shaqmughal/seekstone/seekstone"><img src="https://agentmods.dev/badge/mcp/shaqmughal/seekstone/seekstone/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/shaqmughal/seekstone/seekstone"><img src="https://agentmods.dev/badge/mcp/shaqmughal/seekstone/seekstone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seekstone 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 9d 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
{
"seekstone": {
"command": "npx",
"args": [
"-y",
"seekstone"
],
"env": {
"SEEKSTONE_VAULT": ""
}
}
}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.
- 9d ago First seen · 12 lines scan A 244b3879bd94
seekstone is an MCP server published in the GitHub repository shaqmughal/seekstone (25 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
spoken
Podcast transcripts as clean Markdown with real speaker names — via the Spoken API. Runs locally from the spoken-mcp npm package. Needs 1 environment variable to run.
markdown-document-search
Convert document collections to verified Markdown, package them encrypted, and expose them to agents over MCP. Runs locally from the mdcx Python package. Needs 2 environment variables to run.
mdcx
Convert document collections to verified Markdown, package them encrypted, and expose them to agents over MCP. Runs locally from the mdcx Python package. Needs 2 environment variables to run.
jdocmunch-mcp
Token-efficient MCP server for structured documentation retrieval via section-level indexing. Runs locally from the jdocmunch-mcp Python package.
docsift
Convert documents once. Give agents only what they need. Runs locally from the docsift Python package.
agentdocs-mcp
MCP server for AgentDocs (agentdocs.eu): read, search, write, comment on & share Markdown docs. Runs locally from the agentdocs-mcp npm package. Needs 2 environment variables to run.