Alpaca Trading API integration for Model Context Protocol (MCP)
Latam is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Catalog, prices, items, compliance and Siigo data by country, live for AI agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http siigolatam-latam-mcp https://mcp.siigolatam.com/mcp
# 2 — ask your agent for something these tools do
# get_page_structured_data, get_products, search and 3 more
Latam costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http siigolatam-latam-mcp https://mcp.siigolatam.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
| 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-invent |
Returns Siigo's catalog of products/plans for a country with price, currency and feature list, read from the schema.org Product graphs of the pricing page. Use this when the user asks about pricing, plans, or what's included in each tier. Example call: {"country": "COL"} (uses the configured default slug precios-siigo). An empty products array means the page currently publishes no Product JSON-LD.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
| slug | string | no | 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 |
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_ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
| 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. |
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:{co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
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 cal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
| regulation | string | no | 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, exog |
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":
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU. |
| topic | string | no | Optional blog category slug. Must be one of the shell's six content categories: contabilidad-finanzas, gestion-administrativa, emprendimiento, derecho-laboral, obligaciones-fiscales, tecnologia-innova |
| limit | integer | no | 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 v |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Latam or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Latam can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.