Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DevDome Analytics

REMOTE · ANALYTICS.DEVDOME.COM · SCANNED SEP 22

Website traffic, bot reports, realtime visitors and site health for your DevDome sites

+4 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 546 tokens (~54/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the DevDome Analytics MCP server?

DevDome Analytics is a hosted endpoint at https://analytics.devdome.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · analytics.devdome.com

# add to Claude Code
claude mcp add --transport http com-devdome-analytics 'https://analytics.devdome.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-devdome-analytics": {
      "url": "https://analytics.devdome.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-devdome-analytics": {
      "type": "http",
      "url": "https://analytics.devdome.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-devdome-analytics]
url = "https://analytics.devdome.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-devdome-analytics": {
      "type": "remote",
      "url": "https://analytics.devdome.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-devdome-analytics --url 'https://analytics.devdome.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-devdome-analytics:
    url: "https://analytics.devdome.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-devdome-analytics": {
      "Transport": "http",
      "Url": "https://analytics.devdome.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-devdome-analytics -t streamable-http -u 'https://analytics.devdome.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-devdome-analytics": {
      "type": "http",
      "url": "https://analytics.devdome.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1
    • Stability: unverified → 0.03 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://analytics.devdome.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=devdome.com CN=WE1,O=Google Trust Services,C=US 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA256 95b632de429f9cba134dc785deb41c72
SANs: devdome.com, analytics.devdome.com, *.analytics.devdome.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of analytics.devdome.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
devdome.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://analytics.devdome.com/mcp Verified 200
http (plaintext) http://analytics.devdome.com/mcp HTTPS enforced 301 https://analytics.devdome.com/mcp
MCP tools · 10 exposed · ~499 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_site ~45

Add a website to the account. Returns the tracking snippet to install; the site stays pending until verified.

NameTypeReqDescription
domainstringyesThe bare domain, e.g. example.com

No output schema declared.

No examples provided.

get_bot_report ~71

Bot traffic on a site - DevDome separates every hit into human vs bot. kind 'bots' = known-bot catalog activity; 'threats' = suspicious/behavioral detections.

NameTypeReqDescription
daysnumber
kindstring
sitestringyes

No output schema declared.

No examples provided.

get_breakdown ~62

Top-N breakdown of a site's traffic by one dimension.

NameTypeReqDescription
daysnumber
dimensionstringyes
fromstring
limitnumber
sitestringyes
tostring

No output schema declared.

No examples provided.

get_realtime ~35

Visitors active on the site in the last 5 minutes, with their current page and path.

NameTypeReqDescription
sitestringyes

No output schema declared.

No examples provided.

get_site_health ~37

Uptime/health summary for a site: status, response time, TLS/domain checks, open incidents.

NameTypeReqDescription
sitestringyes

No output schema declared.

No examples provided.

get_stats ~85

Headline KPIs for a site: visits, visitors, pageviews, outbound clicks, bots, CTR, bounce rate, session duration. Defaults to the full retained history.

NameTypeReqDescription
daysnumberWindow in days (omit for full history)
fromstringYYYY-MM-DD
sitestringyes
tostringYYYY-MM-DD

No output schema declared.

No examples provided.

get_timeseries ~63

Daily traffic series for a site (visits, visitors, pageviews, clicks, bots per day, in the site's timezone).

NameTypeReqDescription
daysnumber
fromstring
sitestringyes
tostring

No output schema declared.

No examples provided.

get_visitors ~48

Recent individual visits: entry page, path taken, country, device, human/bot.

NameTypeReqDescription
daysnumber
limitnumber
sitestringyes

No output schema declared.

No examples provided.

list_sites ~22

List the websites on this DevDome account with their verification status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_site ~31

Verify ownership of a pending website (checks the installed snippet or DNS TXT record).

NameTypeReqDescription
domainstringyes

No output schema declared.

No examples provided.

Common questions

What is the DevDome Analytics MCP server?

DevDome Analytics is an MCP server listed in the public MCP registry as com.devdome/analytics. Website traffic, bot reports, realtime visitors and site health for your DevDome sites. This page covers its hosted endpoint (https://analytics.devdome.com/mcp).

Is the DevDome Analytics MCP server safe to use?

DevDome Analytics scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DevDome Analytics MCP server expose?

DevDome Analytics exposes 10 tools: list_sites, add_site, verify_site, get_stats, get_timeseries, and 5 more. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.

Does the DevDome Analytics MCP server require authentication?

Yes. DevDome Analytics asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the DevDome Analytics MCP server still maintained?

DevDome Analytics is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.