Red Atlas Api

red.atlasPublished by atlas.redOfficial publisherv1.0.0Updated Oct 24, 2026

Puerto Rico & Colombia real estate: listings, sales, parcels, permits, analytics, AVM reports.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server giving an assistant access to Puerto Rico and Colombia real estate data: listings, sales, parcels, permits, analytics and AVM reports.

What you can do
Look up property listings and sales records in Puerto Rico and Colombia, including parcel and permit information. Retrieve analytics and automated valuation model (AVM) reports for properties. No individual tools are documented in the supplied material, so exact operations are not confirmed.
When to use it
Useful when an assistant needs property, parcel, permit or valuation information for Puerto Rico or Colombia, for example during real estate research, due diligence or market analysis.
Requirements
A remote streamable HTTP endpoint at apiv3.atlas.red; no local package or runtime is needed. OAuth authentication is required, so an account with the provider is needed. Network access to the endpoint.
Before you install
Access is tied to an OAuth account with the provider, so review what data that account exposes. The material does not state whether tools write, change or delete records, or whether queries are logged or shared with third parties; confirm before relying on it for sensitive property data.

Installation

In SourceWeft

  1. Open Red Atlas Api in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/red.atlas%2Fred-atlas-api/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "red-atlas-api": {
      "type": "http",
      "url": "https://apiv3.atlas.red/external-api/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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
  • 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.

Other Atlas integrations