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.

dev.anotherai/anotherai

REMOTE · API.ANOTHERAI.DEV

MCP server for building and testing AI agents with multi-model experimentation and insights.

Available components

0 this week 0 Trust /100

Last scanned (2 months ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row.

Category AI and Machine Learning

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

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 Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

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.

  • 11 Aug 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
  • 31 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
  • 30 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
  • 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 0

    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 20 Aug 2026 · Probed https://api.anotherai.dev/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Chain error: hostname_mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.azureedge.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US CN=Microsoft TLS G2 ECC CA OCSP 02,O=Microsoft Corporation,C=US 6 Jun 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA384 570002a4cbe1e4c551822886c400000002a4cb
SANs: *.azureedge.net
CN=Microsoft TLS G2 ECC CA OCSP 02,O=Microsoft Corporation,C=US (CA) CN=Microsoft TLS ECC Root G2,O=Microsoft Corporation,C=US 1 Aug 2025 3 Jun 2029 ECDSA 384 ECDSA-SHA384 3300000005516a21c89814ccf7000000000005
CN=Microsoft TLS ECC Root G2,O=Microsoft Corporation,C=US (CA) CN=DigiCert Global Root G3,OU=www.digicert.com,O=DigiCert Inc,C=US 21 May 2025 19 Jun 2029 ECDSA 384 ECDSA-SHA384 8d3c6d001f26cb5a23f0c7d6a73ffb6
CN=DigiCert Global Root G3,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G3,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 ECDSA 384 ECDSA-SHA384 55556bcf25ea43535c3a40fd5ab4572

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.anotherai.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
anotherai.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.anotherai.dev/mcp TLS failed
http (plaintext) http://api.anotherai.dev/mcp Inconclusive 404
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. 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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the dev.anotherai/anotherai MCP server?

dev.anotherai/anotherai is a hosted endpoint at https://api.anotherai.dev/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 · api.anotherai.dev

# add to Claude Code
claude mcp add --transport http dev-anotherai-anotherai 'https://api.anotherai.dev/mcp'
Common questions

What is the dev.anotherai/anotherai MCP server?

dev.anotherai/anotherai is an MCP server listed in the public MCP registry as dev.anotherai/anotherai. MCP server for building and testing AI agents with multi-model experimentation and insights. This page covers its hosted endpoint (https://api.anotherai.dev/mcp).

Does the dev.anotherai/anotherai MCP server require authentication?

Its publisher declares no required credentials for dev.anotherai/anotherai. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the dev.anotherai/anotherai MCP server still maintained?

dev.anotherai/anotherai has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.