Croma
com.usecromaPublished by usecroma.comv1.0.0Updated Oct 24, 2026
Colombian, Peruvian, and Mexican public data: judicial cases, registries, legislation, web search.
The publisher's own server: Cue
Overview
Croma gives an assistant access to Colombian, Peruvian and Mexican public data such as judicial cases, registries and legislation.
- What you can do
- Croma is a remote MCP server that exposes Latin American public data to an assistant. According to its registry description, it covers judicial cases, registries and legislation from Colombia, Peru and Mexico, plus web search. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
- When to use it
- Use it when an assistant needs to look up public records, court cases or legislation from Colombia, Peru or Mexico, or to search the web for related material. It is not aimed at private or non-public data.
- Requirements
- A remote MCP endpoint at over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Croma in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.usecroma%2Fcroma/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"croma": {
"type": "http",
"url": "https://api.croma.run/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
