Mapnostics

io.github.ffteemaPublished by GitHub account ffteemav1.1.0Updated Oct 24, 2026

Codebase intelligence for AI agents — dead code, blast radius, ownership.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Mapnostics gives an AI assistant codebase intelligence: dead code, blast radius and ownership, via a remote endpoint or a local npx process.

What you can do
  • No tool list is published, so capabilities come from the description only.
  • The server is positioned as codebase intelligence for AI agents, covering dead code, blast radius and ownership.
  • It can be reached either as a remote MCP endpoint or as a local process started with npx.
When to use it
Consider it when an assistant needs to reason about a codebase beyond reading files: finding unused code, judging what a change could affect, or identifying who owns a part of the repository.
Requirements
A Mapnostics account and a personal API key, supplied as the MAPNOSTICS_API_KEY environment variable or as an Authorization bearer header. The endpoint defaults to the hosted Mapnostics MCP URL and can be overridden with MAPNOSTICS_URL. The local option runs through npx, so Node.js is needed.
Before you install
The API key is a secret tied to your Mapnostics account and repository settings; keep it out of shared configuration and logs. The server analyzes repository code, so code and repository metadata are sent to the Mapnostics service when using the hosted endpoint.

Installation

In SourceWeft

  1. Open Mapnostics in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.ffteema%2Fmapnostics-mcp/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.

{
  "mcpServers": {
    "mapnostics": {
      "type": "http",
      "url": "https://www.mapnostics.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.