Siigo Latam
REMOTE · MCP.SIIGOLATAM.COM
Catálogo, precios, artículos, compliance y datos de Siigo por país, en vivo para agentes de IA.
Available components
Last scanned (10 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1562 tokens (~260/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- Tool “get_products” rewrote its description, which is the text the model reads security
- Schema quality: 233 → 260 ▼ functional
- “get_articles” reworded the description of “country” cosmetic
- “get_compliance_info” reworded the description of “country” cosmetic
- “get_organization_info” reworded the description of “country” cosmetic
- “get_page_structured_data” reworded the description of “country” cosmetic
- “get_products” reworded the description of “country” cosmetic
- “search” reworded the description of “country” cosmetic
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Server version: 1.0.0 → 1.1.0 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Server version: 1.1.0 → 1.0.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.siigolatam.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=siigolatam.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 72ccf6806c73829a13c3a9bfd4a3ac56 |
| SANs: siigolatam.com, *.siigolatam.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.siigolatam.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| siigolatam.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src https: data: blob: 'self'; script-src https: 'unsafe-inline' 'unsafe-eval'; style-src https: 'unsafe-inline'; img-src https: data: blob:; font-src https: data:; connect-src https: wss: data: blob:; frame-src https: data: blob:; object-src https: data:; media-src https: blob:; worker-src https: blob:; frame-ancestors 'self'; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), fullscreen=(*), payment=(*), usb=(), clipboard-read=(self), clipboard-write=(self), local-fonts=(self), vr=(), autoplay=(self), screen-wake-lock=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.siigolatam.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.siigolatam.com/mcp | HTTPS enforced | 301 | https://mcp.siigolatam.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_articles ~295
Returns recent Siigo blog articles for a country, optionally filtered by topic. Each item has slug, title, excerpt, author, date, category, URL and the schema.org BlogPosting JSON-LD. Use this when the user wants up-to-date Siigo perspectives on accounting, taxes, PYMEs, fintech or product launches. Example calls: {"country": "COL", "limit": 10} for the latest across every category, or {"country": "COL", "topic": "derecho-laboral", "limit": 5} for one category.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
| limit | integer | – | Optional max number of articles to return. Default 10. Keep it at 25 or below: articles are fetched with the author embedded and WordPress silently returns an empty payload past ~25 items, so higher… |
| topic | string | – | Optional blog category slug. Must be one of the shell's six content categories: contabilidad-finanzas, gestion-administrativa, emprendimiento, derecho-laboral, obligaciones-fiscales, tecnologia-innov… |
No output schema declared.
No examples provided.
get_compliance_info ~304
Returns tax-and-regulatory compliance information for Siigo's country (Colombia DIAN: RADIAN, UGPP, documento soporte, electronic invoicing rules; Mexico SAT: CFDI 4.0, Carta Porte, DIOT, timbrado). Each item exposes title, summary, last updated date, source URL and the schema.org BlogPosting JSON-LD. Use this when the user asks about Siigo's compliance posture or specific regulations. Example calls: {"country": "COL"} or {"country": "MEX"} for the full list, or {"country": "MEX", "regulation": "CFDI"} to narrow it down.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
| regulation | string | – | Optional single-word filter forwarded to WordPress full-text search. Letters, digits, hyphen and underscore only — no spaces, max 100 chars. Working examples — Colombia: RADIAN, UGPP, IVA, renta, exo… |
No output schema declared.
No examples provided.
get_organization_info ~179
Returns canonical Organization data for Siigo in a country: legal name, URL, logo, social profiles (sameAs), address, phone and founding date — plus the full schema.org JSON-LD graphs for the 'about / por qué' page. Use this when the agent needs trustworthy company facts to cite Siigo as a source. Example call: {"country": "COL"}. The data is read from the country's home page (ContentProviders:{country}:Webapp:OrganizationSlug, COL: inicio), the only page that publishes the Organization graph; LocalBusiness and Corporation count as well.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
No output schema declared.
No examples provided.
get_page_structured_data ~253
Returns the curated JSON-LD structured data graphs (Service, SoftwareApplication, Product, Offer, Review, FAQ, Breadcrumb…) for a Siigo landing page, plus SEO metadata. Use this when the user asks about a specific Siigo product or topic and you want canonical, schema.org-ready data. Example call: {"country": "COL", "slug": "facturacion-electronica"}. Pages with no JSON-LD still return title + seo with an empty jsonLdGraphs array.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
| slug | string | yes | WordPress page slug, without leading slash. Lowercase letters, digits and hyphens only, max 200 chars. Real COL slugs: facturacion-electronica, nomina-electronica, software-contable, gestion-de-inven… |
No output schema declared.
No examples provided.
get_products ~339
Returns Siigo's catalog of products/plans for a country with price, currency and feature list, read from the pricing page (its schema.org Product graphs, or the shell catalogue where the country publishes one). Use this when the user asks about pricing, plans, discounts or what's included in each tier. `price` is the list price of the headline plan (yearly when there is one) and never includes a discount. `offers` holds every published price; an offer whose description ends in "con descuento" is a discount in force, with `regularPrice` (the list price it replaces) and `discountPercent` when the source publishes them. `monthlyEquivalent` is the per-month figure the pricing card shows for a multi-month plan (period total divided by its months), not the price of the monthly plan. Example call: {"country": "COL"} (uses the configured default slug precios-siigo). An empty products array means the page currently publishes no products.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
| slug | string | – | Optional WP page slug whose JSON-LD exposes the Product/Offer graphs. Defaults to ContentProviders:{country}:ProductsSlug (COL: precios-siigo). Ignored for countries whose shell publishes a catalogue… |
No output schema declared.
No examples provided.
search ~192
Full-text search against Siigo's curated content for a country. Returns matching pages, posts, and resources. Use this when the user mentions a topic you don't have a more specific tool for. Example call: {"country": "COL", "query": "facturacion electronica"}. Note: the COL shell has search disabled until its cached search service ships, so it currently returns an empty items array — prefer get_articles or get_compliance_info meanwhile.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY. |
| query | string | yes | Free-text query against Siigo's WordPress content. Between 2 and 200 chars, no angle brackets. Examples: facturacion electronica, nomina, plan emprendedor. |
No output schema declared.
No examples provided.
How do I install the Siigo Latam MCP server?
Siigo Latam is a hosted endpoint at https://mcp.siigolatam.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.siigolatam.com
claude mcp add --transport http com-siigolatam-siigo 'https://mcp.siigolatam.com/mcp'
What is the Siigo Latam MCP server?
Siigo Latam is an MCP server listed in the public MCP registry as com.siigolatam/siigo. Catálogo, precios, artículos, compliance y datos de Siigo por país, en vivo para agentes de IA. This page covers its hosted endpoint (https://mcp.siigolatam.com/mcp).
Is the Siigo Latam MCP server safe to use?
Siigo Latam scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Siigo Latam MCP server expose?
Siigo Latam exposes 6 tools: get_page_structured_data, get_products, search, get_organization_info, get_compliance_info, get_articles. Their descriptions and schemas cost roughly 1,562 tokens of context every time the server is loaded.
Does the Siigo Latam MCP server require authentication?
No. We connected to Siigo Latam without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Siigo Latam MCP server still maintained?
Siigo Latam is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Siigo Latam MCP server?
VerifyMCP ran 12 checks on Siigo Latam, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Siigo Latam: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.