Simplr Ai Dev MCP Server
@simplr-ai/dev-mcp
npm
v1.4.4
Published by @simplr-ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Simplr Dev MCP - help AI coding agents integrate every Simplr feature (guides, snippets, live verification)
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([list_flags]) co-exist with external-action tools ([create_webhook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [list_flags] → sinks [create_webhook]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow list_flags → create_webhook
medium Unconstrained URL/host parameter "url" on "create_webhook"MTC-CAP-007
Tool "create_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool create_webhook · inputSchema.properties.url
Tools 50
Each tool and what it can reach — statically extracted from the published source.
create_webhooknetwork egresslist_flagsingests untrusted inputapply_automation_setupno sensitive capabilityassess_performance_and_experienceno sensitive capabilityattach_test_evidenceno sensitive capabilityclaim_feedbackno sensitive capabilityclaim_self_healing_incidentno sensitive capabilitycode_review_setup_guideno sensitive capabilitycomment_feedbackno sensitive capabilitycomplete_test_verificationno sensitive capability
Show 40 more tools ↓
configure_environment_mappingno sensitive capabilityconfigure_github_automation_policyno sensitive capabilityconnect_google_cloud_loggingno sensitive capabilityconnect_incident_ai_providerno sensitive capabilityconnect_mongodb_investigationno sensitive capabilitycreate_feature_flagno sensitive capabilitycreate_test_verificationno sensitive capabilityevaluate_self_healing_actionno sensitive capabilityexecute_github_operationno sensitive capabilityget_agent_coding_standardsno sensitive capabilityget_api_referenceno sensitive capabilityget_automation_setup_planno sensitive capabilityget_code_snippetno sensitive capabilityget_feedbackno sensitive capabilityget_incident_escalation_contextno sensitive capabilityget_integration_guideno sensitive capabilityget_quickstartno sensitive capabilityget_self_healing_incidentno sensitive capabilityinspect_automation_setupno sensitive capabilityinspect_github_automationno sensitive capabilityinvestigate_self_healing_incidentno sensitive capabilitylease_test_credentialno sensitive capabilitylist_featuresno sensitive capabilitylist_feedbackno sensitive capabilitylist_self_healing_incidentsno sensitive capabilityload_code_review_standardno sensitive capabilityrelease_feedbackno sensitive capabilityreport_agent_standard_outcomeno sensitive capabilityrequest_ai_code_reviewno sensitive capabilityrequest_github_operationno sensitive capabilityrun_automation_templateno sensitive capabilityrun_checkno sensitive capabilitysearch_docsno sensitive capabilitysend_automation_test_eventno sensitive capabilitystart_test_verificationno sensitive capabilitysubmit_review_fix_learningno sensitive capabilitytest_incident_connectionno sensitive capabilityupdate_feedbackno sensitive capabilityupdate_self_healing_incidentno sensitive capabilityvalidate_api_keyno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (50 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 5
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.4.4 latest |
A 95/100 | 2 | 1.13.0 | 2026-09-07 |
v1.4.3 |
A 95/100 | 2 | 1.12.1 | 2026-08-05 |
v1.4.2 |
A 95/100 | 2 | 1.12.1 | 2026-08-03 |
v1.4.1 |
A 95/100 | 2 | 1.12.1 | 2026-08-01 |
v1.2.0 |
A 95/100 | 2 | 1.12.1 | 2026-07-28 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @simplr-ai/dev-mcp --onlineMore in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).