MCPComp Diagnostics

dev.mcpcompPublished by mcpcomp.devv0.6.1Updated Oct 24, 2026

Grade an MCP server's auth against the spec and diagnose which layer a failure is in.

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: dev.mcpcomp/diagnostics
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mcpcomp.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.mcpcomp%2Fdiagnostics.svg)](https://sourceweft.com/mcp/dev.mcpcomp%2Fdiagnostics?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that grades an MCP server's authentication against the spec and diagnoses which layer a failure is in.

What you can do: Grades an MCP server's auth setup against the specification.
Diagnoses which layer a failure is occurring in.
No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it: Useful when building or reviewing an MCP server and you want to check whether its authentication matches the spec, or when an auth failure needs to be traced to a specific layer.
Requirements: Runs as a local process over stdio, installed from the npm package mcpcomp, so Node.js and npm are needed. Desktop-only; no web execution. No authentication, environment variables or headers are declared.

Before you install

No credentials, write actions or third-party data sharing are declared. The tool list is not published, so review what it inspects before running it against a server whose configuration may be sensitive.

Installation

In SourceWeft

Open MCPComp Diagnostics in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.6.1LatestSep 16, 2026

Score

15% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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.
License10 pts
Declare a license in the repository or the registry entry.