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/tersignhq/tersign-jsWrote 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/tersignhq/tersign-js/evidence)<a href="https://agentmods.dev/mcp/tersignhq/tersign-js/evidence"><img src="https://agentmods.dev/badge/mcp/tersignhq/tersign-js/evidence.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
evidence 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 6d 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
{
"evidence": {
"command": "npx",
"args": [
"-y",
"tersign"
],
"env": {
"TERSIGN_SELLER_KEY": "",
"TERSIGN_ISSUER_NAME": "",
"TERSIGN_ISSUER_JURISDICTION": "",
"TERSIGN_ISSUER_TAX_ID": "",
"TERSIGN_LEDGER_URL": "",
"TERSIGN_LEDGER_API_KEY": "",
"TERSIGN_LEDGER_SELLER_ID": ""
}
}
}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.
- 6d ago First seen · 18 lines scan A 940f5f016faa
evidence is an MCP server published in the GitHub repository tersignhq/tersign-js (1 stars, last pushed 7d 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
sanctionsai
OFAC sanctions screening for AI agents: screen names, wallets, entities against the SDN list. Remote server at sanctionsai.dev.
dingdawg-legal-agent
AI contract review, clause drafting, compliance checklists & legal research. Runs locally from the dingdawg-legal-agent npm package. Needs 1 environment variable to run.
dingdawg-governance
Governance receipts for AI agents — universal, MCP-native, fail-closed governance layer compliant with EU AI Act Art. 12, Colorado AI Act (SB 24-205), and NIST AI RMF. LNN interpretability, IPFS audit proofs, and rollback for any agent in any framework. Runs locally from the dingdawg-governance npm package. Needs 1…
eu-audit-mcp
Tamper-evident audit trail MCP server for EU AI Act and GDPR compliance. Runs locally from the eu-audit-mcp Python package. Needs 1 environment variable to run.
dingdawg-compliance
EU AI Act + Colorado AI Act compliance scoring. 87/100 in 60 seconds. Free local scan. Runs locally from the dingdawg-compliance npm package. Needs 1 environment variable to run.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.