1. Conduid
  2. Scraping
  3. Travel Risk Intelligence MCP
MCP server · Scraping

Travel Risk Intelligence MCP

by · github.com/apifyforge/travel-risk-intelligence-mcp

Travel risk intelligence for any global destination, delivered through 8 MCP tools backed by real-time government and international data sources.

Unclaimed last commit 7 months ago ai-toolsapifyclaudecursormcpmcp-servermodel-context-protocolwindsurf
InstallView source
34Low

Scored 13 hours ago · breakdown

About Travel Risk Intelligence MCP

Travel Risk Intelligence MCP is an MCP server published by apifyforge in the Scraping category: travel risk intelligence for any global destination, delivered through 8 MCP tools backed by real-time government and international data sources.

The repository has 1 stars and 0 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/apifyforge/travel-risk-intelligence-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Travel Risk Intelligence MCP

Powered by Claude · Grounded in docs

I know everything about Travel Risk Intelligence MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Travel Risk Intelligence MCP

How do I install Travel Risk Intelligence MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Travel Risk Intelligence MCP safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Travel Risk Intelligence MCP still maintained?

The last commit was 7 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.