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.

Agency Standings

REMOTE · AGENCYSTANDINGS.COM

Evidence-based agency rankings for Ecom, Legal, SaaS, Finance and Service, plus a work library.

0 this week 85 Trust /100

Last scanned (13 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1476 tokens (~210/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 15 Nov 26 0
    • Stability: 0.97 → pass security
  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_agency” rewrote its description, which is the text the model reads security
    • Tool “get_methodology” rewrote its description, which is the text the model reads security
    • Tool “search_agencies” rewrote its description, which is the text the model reads security
  • 8 Nov 26 +1

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

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

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

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 21 Nov 2026 · Probed https://agencystandings.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.agencystandings.com CN=YR2,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 RSA 2048 SHA256-RSA 646c9a5703e6e11b3fb15ffd9d76b1e3ba3
SANs: *.agencystandings.com, agencystandings.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agencystandings.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agencystandings.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agencystandings.com/mcp Verified 200
http (plaintext) http://agencystandings.com/mcp HTTPS enforced 308 https://agencystandings.com/mcp
MCP tools · 7 exposed · ~1,135 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
get_agency ~105

Return the evidence review for one agency slug: its supported exact industry rank, published band, or unranked standing, services, source URLs and retrieval dates, profile URL, and contact URL. Filtering does not change the published rank or band. No numeric score.

NameTypeReqDescription
slugstringyesAgency slug, such as blend-commerce.
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

No output schema declared.

No examples provided.

get_methodology ~128

Explain how Agency Standings publishes ranks. Real rankings, earned through evidence: client results, testimonials and published work. Agencies never pay for rankings, briefs or hires, and cannot sponsor or buy a newsletter spot. Rankings depend on evidence. Agencies can never sponsor or advertise on Agency Standings or the Big Moves newsletter. Sponsors are products, software tools, AI companies and other non-agency brands. Rank numbers are included. A numeric score is not.

NameTypeReqDescription
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

No output schema declared.

No examples provided.

get_started ~92

Start here. Ask whether the user is a brand looking for an agency or an agency that wants to join. Brand path uses the search tools. Agency path uses join_as_agency, then the private agency tools after the profile is claimed. Qualified briefs are not open yet.

NameTypeReqDescription
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

No output schema declared.

No examples provided.

join_as_agency ~203

Store a pending agency application. Collect the agency name, https website, contact email, industries, services, and a city or region. Do not collect a phone number or street address. We review the evidence before listing or ranking. No one can pay to be ranked. Rankings come only from evidence.

NameTypeReqDescription
agencyNamestringyesAgency name.
contactEmailstringyesContact email for the application.
industriesarrayyesIndustry labels or slugs: Ecom, SaaS, Legal, Finance, Service.
locationstringyesCity or region. Do not send a street address or phone number.
servicesarrayyesService labels or slugs, such as SEO or Web Design.
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).
websitestringyesAgency website. https is added when the scheme is missing.

No output schema declared.

No examples provided.

list_industries_and_services ~77

List industries and service types. Ecom, Legal, SaaS, Finance, and Service are ranked. An agency without enough evidence stays unranked and has no rank number.

NameTypeReqDescription
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

No output schema declared.

No examples provided.

search_agencies ~334

Search Agency Standings. Each result includes its industry, services, evidence level, a one-line evidence summary, profile URL, and contact URL. A plain-language query drops filler words such as agency, firm, best, and top, maps words such as lawyer, Shopify, or software onto an industry, and ranks agencies that match any remaining word. If a location matches nobody, that location is left off and the response includes a note. Ecom and Service use alphabetical bands. Legal, SaaS and Finance expose exact top-three places, then alphabetical bands. Agencies without enough evidence stay unranked and have no rank number. A service, location, or zip filter preserves published ranks and bands; it never renumbers matches. get_agency keeps each agency's published industry rank or band. Results do not include a numeric score.

NameTypeReqDescription
industrystring–Industry slug or label, such as ecom or Legal.
limitinteger–Maximum results to return. Defaults to 10.
locationstring–City, state, or country. Matches state abbreviations and full names, cities, and country names against a sourced headquarters or other listed office.
querystring–Plain language or words matched against the name, services, and evidence summary. Filler words are ignored.
servicestring–Service slug or label, such as seo or Web Design.
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).
zipstring–Postal code matched against a stored headquarters string.

No output schema declared.

No examples provided.

search_work ~196

Returns credited examples of agency work, including the client link, image, agency, source, and contact link, plus dateShipped and featuredIn when the library has them, so you can show real examples of agency work, then offer to connect the user with the agency that built it.

NameTypeReqDescription
industrystring–Industry label, such as Ecom.
limitinteger–Maximum results to return. Defaults to 10.
platformstring–Platform, such as Shopify or Shopify Plus.
querystring–Words matched against the client, agency, platform, and services.
servicestring–Service tag, such as Development or SEO.
typestring–Work type: website, product page, ad creative, video, or branding.
user_requeststring–A short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

No output schema declared.

No examples provided.

Install

How do I install the Agency Standings MCP server?

Agency Standings is a hosted endpoint at https://agencystandings.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 · agencystandings.com

# add to Claude Code
claude mcp add --transport http com-agencystandings-agency-standings 'https://agencystandings.com/mcp'
Common questions

What is the Agency Standings MCP server?

Agency Standings is an MCP server listed in the public MCP registry as com.agencystandings/agency-standings. Evidence-based agency rankings for Ecom, Legal, SaaS, Finance and Service, plus a work library. This page covers its hosted endpoint (https://agencystandings.com/mcp).

Is the Agency Standings MCP server safe to use?

Agency Standings scores 85 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 Agency Standings MCP server expose?

Agency Standings exposes 7 tools: get_started, join_as_agency, search_agencies, search_work, get_agency, and 2 more. Their descriptions and schemas cost roughly 1,135 tokens of context every time the server is loaded.

Does the Agency Standings MCP server require authentication?

No. We connected to Agency Standings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agency Standings MCP server still maintained?

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

What did VerifyMCP test on the Agency Standings MCP server?

VerifyMCP ran 13 checks on Agency Standings, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.