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

Agentda

REMOTE · MYAGENTDA.COM · SCANNED AUG 3

Agent-native task management: your AI agent is the interface. Delegate to anyone by email.

Available components

remote · myagentda.com 39
+14 this week 39 Trust /100
Trust breakdown (6 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 →

Endpoint Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · myagentda.com

# add to Claude Code
claude mcp add --transport http com-myagentda-agentda https://myagentda.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.com-myagentda-agentda]
url = "https://myagentda.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-myagentda-agentda": {
      "type": "remote",
      "url": "https://myagentda.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-myagentda-agentda --url https://myagentda.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-myagentda-agentda:
    url: "https://myagentda.com/api/mcp"
// mcp.json
{
  "mcpServers": {
    "com-myagentda-agentda": {
      "type": "http",
      "url": "https://myagentda.com/api/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.

  • 31 Jul 26 +14
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 25

    First indexed and scored.

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 3 Aug 2026 · Probed https://myagentda.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=myagentda.com CN=WE1,O=Google Trust Services,C=US 19 Jul 2026 17 Oct 2026 ECDSA 256 ECDSA-SHA256 bb8f0d8a5c086cfc13c0a462dd2b5d18
SANs: myagentda.com, *.myagentda.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
DNSSEC secure

Validation of myagentda.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
myagentda.com. present 2371 13 Verified
myagentda.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://myagentda.com/.well-known/oauth-protected-resource" 

Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://myagentda.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000
www-authenticate Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://myagentda.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://myagentda.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://myagentda.com
Authorisation server https://myagentda.com
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://myagentda.com/api/mcp Auth required 401
http (plaintext) http://myagentda.com/api/mcp HTTPS enforced 308 https://myagentda.com/api/mcp
MCP tools

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.

No tool schema has been captured from this endpoint yet.