B+

api.searchcode.com

Item: api.searchcode.com
Rating: 87
Author: wmcp.sh

https://api.searchcode.com/v1/mcp

87/100 · MCP Trust Grade · checked 6h ago · MCP 2025-03-26

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 6 tools · Developer Tools

code_analyze

Instant repo overview — languages, complexity, file count, tech stack, code quality findings, and credential scanning. Use as your first call to under

code_search

Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy

code_get_file

Get code from a remote public git repository — either a specific function/class by name, a line range, or a full file. PREFERRED WORKFLOW: When search

code_file_tree

List files and directories in any public git repo. Supports fuzzy file search (query parameter), language/path filtering, and depth control. Combine q

code_get_files

Get contents of multiple files from a remote public git repository in a single call. Reduces round-trips when you need to read several related files.

code_get_findings

Get detailed code quality findings from a remote public git repository. Returns rule IDs, line numbers, severity, category, descriptions, and source s

Spec conformance20%100

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 6 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

6 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 1739ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%80

100% of tools have typed inputSchema
0/6 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade api.searchcode.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — api.searchcode.com grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/api.searchcode.com

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/api.searchcode.com/badge.svg)](https://wmcp.sh/mcp/grade/api.searchcode.com)

HTML

<a href="https://wmcp.sh/mcp/grade/api.searchcode.com"><img src="https://wmcp.sh/mcp/grade/api.searchcode.com/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.