REMAP

ai.mdilPublished by mdil.aiOfficial publishervREMAP-MCP-1Updated Oct 29, 2026

Up to 90% fewer tokens: deterministic, declared tool calls, each with a receipt and an audit trail.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

REMAP is a remote MCP endpoint that serves deterministic, declared tool calls with receipts and an audit trail, claiming up to 90% fewer tokens.

What you can do
  • Issues declared tool calls that are deterministic rather than model-improvised.
  • Returns a receipt for each call and keeps an audit trail of what was executed.
  • Aims to cut token usage by up to 90% compared with ordinary tool calling.
  • Connects as a hosted remote endpoint over streamable HTTP; no tool list is published in the manifest.
When to use it
Consider it when you want tool calls that are declared and reproducible, and need receipts or an audit trail of what an assistant executed. It may also suit setups where token cost of tool use is a concern.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Access is gated by OAuth, so an account with the provider is involved. The server records receipts and an audit trail of tool calls, which means activity data is retained by the provider. The tool set is not documented in the manifest, so review what it can execute before granting access.

Installation

In SourceWeft

  1. Open REMAP 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/ai.mdil%2Fremap/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": {
    "remap": {
      "type": "http",
      "url": "https://remap.mdil.ai/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. vREMAP-MCP-1LatestOct 29, 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.