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/SignaTrustDev/signatrust-mcpWrote 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/signatrustdev/signatrust-mcp/mcp-server)<a href="https://agentmods.dev/mcp/signatrustdev/signatrust-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/signatrustdev/signatrust-mcp/mcp-server/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/signatrustdev/signatrust-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/signatrustdev/signatrust-mcp/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@signatrust/mcp-server"
],
"env": {
"SIGNATRUST_API_KEY": "",
"SIGNATRUST_API_URL": ""
}
}
}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 · 13 lines scan A 1d1c7fd7ce6e
mcp-server is an MCP server published in the GitHub repository SignaTrustDev/signatrust-mcp (1 stars, last pushed 3mo 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
dottedsign-mcp
Automate eSignature workflows and signing tasks via natural language commands. Remote server at mcp.dottedsign.com.
copilot-mcp
Web3 founder diligence: code audit, jurisdiction, fund matching, portfolio, scoring. Runs locally from the @apexfdn/copilot-mcp npm package. Needs 2 environment variables to run.
electronica
Firma electrónica argentina (Ley 25.506): enviar documentos a firmar, seguir estado y validar. Remote server at electronica.identik.me.
firma
Firma digital argentina (Ley 25.506) con certificados de certificador licenciado. Remote server at firma.identik.me.
attestix
Attestix - Attestation Infrastructure for AI Agents. DID-based agent identity, W3C Verifiable Credentials, EU AI Act compliance, delegation chains, and reputation scoring. 47 MCP tools across 9 modules. Runs locally from the attestix Python package.
iroha-taira
MCP server "iroha-taira", hosted remotely at taira.sora.org, as configured in hyperledger-iroha/iroha.