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/FurlPay/furlpay-travel-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/furlpay/furlpay-travel-mcp/travel-mcp)<a href="https://agentmods.dev/mcp/furlpay/furlpay-travel-mcp/travel-mcp"><img src="https://agentmods.dev/badge/mcp/furlpay/furlpay-travel-mcp/travel-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/furlpay/furlpay-travel-mcp/travel-mcp"><img src="https://agentmods.dev/badge/mcp/furlpay/furlpay-travel-mcp/travel-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
travel-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 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
{ "travel-mcp": { "command": "npx", "args": [ "-y", "@furlpay/travel-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.
- 1mo ago First seen · 9 lines scan A f4febd342334
travel-mcp is an MCP server published in the GitHub repository FurlPay/furlpay-travel-mcp (0 stars, last pushed 1mo 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-09-01.
Other mcp servers, from other repositories
liteapi
MCP server "liteapi", hosted remotely at mcp.liteapi.travel, as configured in borski/travel-hacking-toolkit.
mcp
Argentine business automation: Mercado Pago, AFIP/ARCA, WhatsApp, banking, shipping (7 packages). Runs locally from the @ar-agents/mcp npm package. Needs 6 environment variables to run.
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.
mcp-server-vibes-coded
Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools. Remote server at vibes-coded-mcp-production.up.railway.app.
agent-commerce-mcp
Agent Commerce MCP — agent-native A2A storefront. Discovery, Stripe checkout, affiliate program. Runs locally from the agent-commerce-mcp npm package.
ai-data-marketplace
Find and buy x402 agent readiness, vendor risk, transaction, and company intelligence APIs. Runs locally from the dopaminedesk-ai-data-marketplace-mcp npm package.