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/tiefeiyu/PortalWrote 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/tiefeiyu/portal/portal-mcp)<a href="https://agentmods.dev/mcp/tiefeiyu/portal/portal-mcp"><img src="https://agentmods.dev/badge/mcp/tiefeiyu/portal/portal-mcp/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/tiefeiyu/portal/portal-mcp"><img src="https://agentmods.dev/badge/mcp/tiefeiyu/portal/portal-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
portal-mcp 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 11d 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
{ "portal-mcp": { "command": "uvx", "args": [ "portal-mcp" ] } }
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.
- 11d ago First seen · 8 lines scan A 64413dff476b
portal-mcp is an MCP server published in the GitHub repository tiefeiyu/Portal (1 stars, last pushed 4d 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
mcp-neo4j-cypher
A simple Neo4j MCP server. Runs locally from the mcp-neo4j-cypher Python package. Needs 9 environment variables to run.
mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server. Runs locally from the mcp-neo4j-memory Python package. Needs 5 environment variables to run.
mcp-neo4j-aura-manager
MCP Neo4j Aura Database Instance Manager. Runs locally from the mcp-neo4j-aura-manager Python package. Needs 3 environment variables to run.
haiku-rag
Local-first agentic RAG with citations - hybrid search, reranking and multimodal retrieval over your own documents, no database server required. Runs locally from the haiku-rag Python package.
airtable-mcp-server
Read and write access to Airtable database schemas, tables, and records. Runs locally from the airtable-mcp-server npm package. Needs 1 environment variable to run.
greptimedb-mcp-server
MCP server for GreptimeDB with SQL/TQL/PromQL support, sensitive data masking, and prompt templates for observability data analysis. Runs locally from the greptimedb-mcp-server Python package. Needs 12 environment variables to run.