What are the risks of connecting to devadex.com?

No blocking issues were found in the static + spec checks. Overall trust grade B (86/100).

When was devadex.com last audited?

Last checked 2026-07-26; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

devadex.com

Item: devadex.com
Rating: 86
Author: wmcp.sh

https://devadex.com/mcp

86/100 · MCP Trust Grade · checked 1d ago · MCP 2025-06-18

Is the devadex.com MCP server safe to use?

Independent trust grade B (86/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches devadex.com for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-07-26 — 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 — 5 tools · Commerce

search_indie

Search independent, small, and newly launched software that mainstream search engines bury. Each result has a `buyUrl` (the link to send the user to —

get_listing

Get full detail for one listing by id, including its outbound url, creator, tags, and popularity/recency signals.

index_stats

How much of the independent-software index is available: total listings, how many are fresh or small, and the top sources, languages and tags.

search_middleware

Search reusable software middleware by CAPABILITY (what it does) across every platform — e.g. 'dialogue', 'authentication', 'inventory', 'networking',

list_capabilities

List the middleware capabilities Devadex indexes (dialogue, auth, inventory, networking, memory, …) with how many middleware exist for each, plus the

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 5 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

5 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%84

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

Tool hygiene15%56

60% of tools have typed inputSchema
0/5 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

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 devadex.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run devadex.com? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

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 — devadex.com grade B

Share on X Open card image

https://www.wmcp.sh/mcp/grade/devadex.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://www.wmcp.sh/mcp/grade/devadex.com/badge.svg)](https://www.wmcp.sh/mcp/grade/devadex.com)

HTML

<a href="https://www.wmcp.sh/mcp/grade/devadex.com"><img src="https://www.wmcp.sh/mcp/grade/devadex.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://www.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.