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/forgemeshlabs/travel-agent-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/forgemeshlabs/travel-agent-mcp/travel-agent)<a href="https://agentmods.dev/mcp/forgemeshlabs/travel-agent-mcp/travel-agent"><img src="https://agentmods.dev/badge/mcp/forgemeshlabs/travel-agent-mcp/travel-agent/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/forgemeshlabs/travel-agent-mcp/travel-agent"><img src="https://agentmods.dev/badge/mcp/forgemeshlabs/travel-agent-mcp/travel-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
travel-agent 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
{
"travel-agent": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/travel-agent-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 · 9 lines scan A af9331a93a84
travel-agent is an MCP server published in the GitHub repository forgemeshlabs/travel-agent-mcp (1 stars, last pushed 9d 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
xcatcher
Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research. Remote server at xcatcher.top.
coinopai-mcp
Kronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base. Runs locally from the coinopai-mcp npm package. Needs 1 environment variable to run.
agent-memory
Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines. Remote server at locker.veritap.dev.
locker
Agent memory that survives you: free to start (any keypair, no signup); opened only by your key. Remote server at locker.veritap.dev.
x402-cloudflare-starter
Model Context Protocol implementation for TypeScript. Runs locally from the @modelcontextprotocol/sdk npm package.
z-zero-mcp
Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context. Runs locally from the z-zero-mcp-server npm package. Needs 1 environment variable to run.