mcpbeat Sign in

Siigo Latam MCP Server

by siigolatam Your server? Claim it
answering

Siigo Latam is answering right now. Last checked 4 min ago.

Catálogo, precios, artículos, compliance y datos de Siigo por país, en vivo para agentes de IA.

Uptime history 7 days of history · worst day 98%
7 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
95 ms
Response time
average over 24h
authentication required
Access
streamable-http

Siigo Latam does not always answer

Over the last week it answered 99.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add siigo --transport http https://mcp.siigolatam.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "siigo": {
      "url": "https://mcp.siigolatam.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.siigo]
url = "https://mcp.siigolatam.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "siigo": {
      "url": "https://mcp.siigolatam.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "siigo": {
      "url": "https://mcp.siigolatam.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://mcp.siigolatam.com/mcp streamable-http needs auth 60 ms 4 min ago

Alternatives to Siigo Latam

same job, measured the same way
Toolcall
by toolcall

30 pay-per-call APIs for AI agents: compliance, trade, safety, web, data. USDC on Base via x402.

20 tools answering
HelpMyAgent
by helpmyagent

Pay-per-call data APIs for AI agents: business, compliance, procurement, VAT and IBAN via x402.

59 tools answering
Execute carbon-tax-compliance-mcp
by evozim

Premium agentic endpoint for carbon-tax-compliance-mcp.

1 tools answering
Execute ashrae-compliance-mcp
by evozim

Premium agentic endpoint for ashrae-compliance-mcp.

1 tools answering
D
DataNexus MCP
by datanexusmcp

Public data intelligence for AI agents — CVE, compliance, patents, contracts, domains.

81 installs/wk 55 tools answering
D
Dropcoin Validation
by freshfos

EU compliance checks for AI agents: sanctions, company, VAT ID, IBAN, email. Pay per call.

6 tools answering
M
meok-compliance-passport-mcp
by csoai-org

Agent Compliance Passport MCP server - portable, signed credentials AI agents carry to prove complia

144 installs/wk local only
Botindex MCP Server
by cyberweasel777

DeFi signal intelligence + agent discovery. Funding arb, whale alerts, Zora, compliance.

55 installs/wk local only

Siigo Latam — questions

Answers built from our own checks of this server.

Why is there no tool list for Siigo Latam?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Siigo Latam working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 95 ms. The bar chart above shows every period we have measured.
How do I connect Siigo Latam?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Siigo Latam need an API key?
Yes. Every time we knock, Siigo Latam answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Siigo Latam?
It answers our handshake in 95 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.