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.

gl.parse/mcp

REMOTE · AGENT.PARSE.GL · 2 COMPONENTS

How ChatGPT and Google AI Mode name, recommend and cite brands.

+5 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 61% 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 Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2382 tokens (~397/item across 6 items; 6 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 Management12
  • Stability check failed: schema churn in the 8 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

  • 21 Nov 26 +4
    • Tool “search_cited_pages” rewrote its description, which is the text the model reads security
    • Tool “query_metrics” rewrote its description, which is the text the model reads security
    • Schema quality: unverified → 100 ▲ functional
    • The server now declares the “prompts” capability functional
    • The server now declares the “resources” capability functional
    • New prompt “start” functional
    • Server version: daed0a57e09f → bef7439da312 functional
    • “search_cited_pages” reworded the description of “pages” cosmetic
    • “get_brief” reworded the description of “kinds” cosmetic
  • 20 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_answers” rewrote its description, which is the text the model reads security
    • Tool “search_cited_pages” rewrote its description, which is the text the model reads security
    • Tool “check_brand” rewrote its description, which is the text the model reads security
    • Tool “query_metrics” rewrote its description, which is the text the model reads security
    • Tool “resolve_ids” rewrote its description, which is the text the model reads security
    • Schema quality: 446 → 392 ▲ functional
    • Server version: f1a4a54a2581 → daed0a57e09f functional
    • “search_answers” added an optional parameter “history” cosmetic
    • “search_cited_pages” added an optional parameter “history” cosmetic
    • “query_metrics” added an optional parameter “history” cosmetic
    • “resolve_ids” reworded the description of “q” cosmetic
    • “get_brief” reworded the description of “kinds” cosmetic
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_brand” rewrote its description, which is the text the model reads security
    • Tool “query_metrics” rewrote its description, which is the text the model reads security
    • Tool “resolve_ids” rewrote its description, which is the text the model reads security
    • Tool “search_answers” rewrote its description, which is the text the model reads security
    • Tool “search_cited_pages” rewrote its description, which is the text the model reads security
    • Schema quality: 503 → 446 ▲ functional
    • Server version: e5bfaeba3303 → f1a4a54a2581 functional
    • “resolve_ids” reworded the description of “q” cosmetic
    • “query_metrics” reworded the description of “explain” cosmetic
    • “resolve_ids” reworded the description of “kinds” cosmetic
    • “query_metrics” dropped the optional parameter “fields” cosmetic
    • “query_metrics” dropped the optional parameter “format” cosmetic
    • “query_metrics” dropped the optional parameter “level” cosmetic
    • “query_metrics” dropped the optional parameter “nudges” cosmetic
    • “query_metrics” dropped the optional parameter “panel” cosmetic
    • “search_answers” dropped the optional parameter “explain” cosmetic
    • “search_answers” dropped the optional parameter “format” cosmetic
    • “search_answers” dropped the optional parameter “level” cosmetic
    • “search_answers” dropped the optional parameter “nudges” cosmetic
    • “search_answers” dropped the optional parameter “view” cosmetic
    • “search_cited_pages” dropped the optional parameter “explain” cosmetic
    • “search_cited_pages” dropped the optional parameter “format” cosmetic
    • “search_cited_pages” dropped the optional parameter “level” cosmetic
    • “search_cited_pages” dropped the optional parameter “minRetrievedBy” cosmetic
    • “search_cited_pages” dropped the optional parameter “nudges” cosmetic
  • 18 Nov 26 0
    • Server version: 35d86653bede → e5bfaeba3303 functional
    • “search_cited_pages” reworded the description of “listsBrand” cosmetic
    • “get_brief” reworded the description of “kinds” cosmetic
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 40f2583e047d → 35d86653bede functional
  • 16 Nov 26 0
    • Server version: 5e933e702285 → 40f2583e047d functional
  • 15 Nov 26 0
    • Stability: 0.03 → fail ▼ security
    • Tool “list_facets” was removed ▼ security
    • Tool “query_metrics” rewrote its description, which is the text the model reads security
    • Tool “resolve_ids” rewrote its description, which is the text the model reads security
    • Tool “search_answers” rewrote its description, which is the text the model reads security
    • Tool “check_brand” rewrote its description, which is the text the model reads security
    • Schema quality: 408 → 493 ▼ functional
    • Tool coverage: 83% → 90% ▲ functional
    • Server version: 6d436f8d3e22 → 5e933e702285 functional
    • “get_brief” added an optional parameter “cursor” cosmetic
    • “get_brief” added an optional parameter “kinds” cosmetic
    • “get_brief” added an optional parameter “limit” cosmetic
    • “get_brief” added an optional parameter “until” cosmetic
    • “get_brief” added an optional parameter “view” cosmetic
    • “resolve_ids” added an optional parameter “match” cosmetic
    • “resolve_ids” added an optional parameter “unit” cosmetic
    • “search_answers” added an optional parameter “rows” cosmetic
    • “search_cited_pages” added an optional parameter “view” cosmetic
    • “get_brief” reworded the description of “since” cosmetic
    • “query_metrics” reworded the description of “measures” cosmetic
    • “resolve_ids” reworded the description of “kinds” cosmetic
    • “resolve_ids” reworded the description of “q” cosmetic
    • “search_answers” reworded the description of “sort” cosmetic
    • “search_answers” reworded the description of “view” cosmetic
    • “query_metrics” made “measures” optional cosmetic
    • “resolve_ids” made “q” optional cosmetic
    • Tool “resolve_ids” changed its title: Resolve names, domains and URLs to ids → Resolve names to ids, find by meaning, list facets cosmetic
    • Tool “search_answers” changed its title: Search AI answers → Search AI answers, or what they say cosmetic
    • Tool “search_cited_pages” changed its title: Search pages AI answers cite → Search pages AI cites, and search result lists cosmetic
    • Tool “get_brief” changed its title: Get the brief → Get the brief, or the event log cosmetic
  • 14 Nov 26 0
    • Tool “check_brand” rewrote its description, which is the text the model reads security
    • Tool “query_metrics” rewrote its description, which is the text the model reads security
    • Tool “search_answers” rewrote its description, which is the text the model reads security
    • Tool “search_cited_pages” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: c7dafc3e2292 → 6d436f8d3e22 functional
    • “get_brief” reworded the description of “moves” cosmetic
    • “query_metrics” reworded the description of “window” cosmetic
    • “search_answers” reworded the description of “window” cosmetic
    • “search_cited_pages” reworded the description of “pages” cosmetic
    • “search_cited_pages” reworded the description of “window” cosmetic
    • “search_cited_pages” dropped the optional parameter “brands” cosmetic
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://agent.parse.gl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=parse.gl CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 cd3ed44471cff86e137d6ce00f56ebee
SANs: parse.gl, *.parse.gl
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 agent.parse.gl. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
gl. DS published 11560 8 Verified
parse.gl. 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=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.parse.gl/mcp Verified 200
http (plaintext) http://agent.parse.gl/mcp HTTPS enforced 301 https://agent.parse.gl/mcp
MCP tools · 6 exposed · ~2,040 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
check_brand ~163

Look up how AI answers talk about a brand, who it loses to, verified product facts, and AI crawler blocks. Call this first for brand positioning, competitor research, AI visibility, or before writing copy about a brand. Takes a website (best), brand name, or brd_ id. Returns data.kind (measured, thin, unplaced, which, unseen): for measured brands, Recommended share (with share_named detail) per market, top rivals, and weakest topic; for ambiguous names (which), the candidate list without reading; for thin/unseen, coverage status and next steps. No brand score. Free.

NameTypeReqDescription
subjectstringyesthe brand's website (best: it settles which company), its name, or a brd_ id

No output schema declared.

No examples provided.

get_brief ~462

Needs a free Parse sign-in, which this call asks the person for: the person's own brand's brief (what changed, what to do next) and their work record. Call it only when the person wants their own brand, tracking or their record, or says yes to an offer; for any public question use check_brand and the other tools.

NameTypeReqDescription
brandstring–the brd_ id of the brand this job is for, in a workspace that serves several (an agency's clients): the brief is about it, nobody is asked which brand is theirs, and nothing is claimed or billed
chainsboolean–add the common jobs, each as its chain of calls (always added while the workspace has no brand)
cursorstring–events only: the page.cursor (an event id) to continue after
kindsarray–events only: only these kinds: mention_move, rival_move, finding, fact_contradicted, page_first_cited, page_dropped, page_changed, proof_step_blocked, own_page_changed, action_outcome, new_answer_bat…
limitinteger–events only: default 25
movesboolean–add every brand of the workspace (its own and those it watches), each in its own markets, this week against the week before, largest move first, one read for all
peekboolean–read the brief without marking it read, so the next call (this key's or another's) still starts where the last read did
sectionsarray–default all
since––"last" (default: since the last brief) or an ISO date or time; with view: "events", a day (UTC), in place of the last 7 days
untilstring–events only: only events on or before this day (UTC)
viewstring–brief (default): what passed the bar, ranked; events: every event

No output schema declared.

No examples provided.

query_metrics ~473

Measure which brands AI names or recommends across topics, markets, or engines. Public measures: answers, questions, share_named, share_recommended, listing_share, concentration (concentration takes no by). Rows include answer and question counts. Shares include a 95% range when available. For cited pages use search_cited_pages. Free. More arguments: resolve_ids {"kinds":["argument"],"q":["query_metrics"]}.

NameTypeReqDescription
brandsarray–with by brand: only these brands' rows, against each other in the same answers (in place of the most named)
byarray–up to 3 of brand, topic, market, question, engine, surface_class, place, country, day, week, month, site, page, page_type, axis, versus_brand, or facet:<key>
comparestring–prior: the window of equal length before, with significance; none: no comparison. Write the value bare, compare: prior, with no quotes inside the string
cursorstring––
explain––false: leave out the one-sentence note (data.note). change (with subject, a share and compare prior): why each share moved, split into the same questions and the question mix, with engine model chang…
filterobject–which answers count; window is a separate argument, not part of filter
historystring–answers past 90 days, $0.001 each once: auto (default) a sample worth up to a quarter of the month's budget, at most $5; all, every answer within the budget; free, none, with each sample's cost
limitinteger–default 25; the token cap wins
measuresarray–required: what to count
sortstring–a measure or a by dimension; "<name> asc" or "<name> desc"
subjectstring–brd_ id the shares are about; or group by brand. With no filter it reads the brand's own markets (up to three) pooled, named in context.marketsRead: pass filter.market for one market's number
windowobject–default the last 28 days; "last" or from/to

No output schema declared.

No examples provided.

resolve_ids ~225

Resolve up to 5 names, domains, URLs, or question wordings to Parse ids, with match scores and brand index status. Use kinds: ["facet"], ["surface"], or ["measure"] for filter values, AI surfaces, or metric definitions. For tool arguments pass kinds: ["argument"] and tool names in q. Free.

NameTypeReqDescription
kindsarray–what to match: brand, topic, question, market, page, site, place (default all); or facet, surface, measure alone for the dictionary; argument alone, with tool names in q: what a tool takes beyond its…
matchstring–name: exact names, domains and ids (the search by meaning needs sign-in)
qarray–up to 5 names, domains, URLs, question wordings or typed ids; the dictionary takes search words or none; kinds argument takes tool names
unitstring–dictionary only: facets of this unit (answer, mention, evidence, comparison, page, page_brand, question, topic_brand)

No output schema declared.

No examples provided.

search_answers ~302

Find AI answers behind a visibility number. Filter by brand, topic, market, question, engine, place, country, citations, keywords, or other facets. Rows include ans_ ids. Use view: "diff" to see brand and citation changes for up to five questions or one topic. For counts and shares use query_metrics. Free. More arguments: resolve_ids {"kinds":["argument"],"q":["search_answers"]}.

NameTypeReqDescription
brandsarray–brd_ ids to mark in text
cursorstring––
fieldsarray–columns to keep in each row
filterobject–which answers count; window is a separate argument, not part of filter
historystring–view: "diff" only: answers past 90 days, $0.001 each once: auto (default) a sample worth up to a quarter of the month's budget, at most $5; all, every answer within the budget; free, none, with each…
limitinteger–default 25; the token cap wins
rowsstring–answers: one row an answer (the sentences and comparisons inside them need sign-in)
sortstring–answers only: relevance (with filter.text; default then), date (default), position (with filter.brand)
windowobject–default the last 28 days; "last" or from/to

No output schema declared.

No examples provided.

search_cited_pages ~415

Find web pages AI cites by brand, topic, market, question, engine, site, or facet. For outreach pass pages: "third_party", filter.brand, and listsBrand: false for pages missing the brand. filter.brandRule: "not_named" selects the answers that omit it. Rows show citation counts, page kind, and whether the page lists that brand when available. Free. More arguments: resolve_ids {"kinds":["argument"],"q":["search_cited_pages"]}.

NameTypeReqDescription
cursorstring––
fieldsarray–columns to keep in each row
filterobject–which answers count; window is a separate argument, not part of filter
historystring–answers past 90 days, $0.001 each once: auto (default) a sample worth up to a quarter of the month's budget, at most $5; all, every answer within the budget; free, none, with each sample's cost
limitinteger–default 25; the token cap wins
listsBrandboolean–needs filter.brand: true keeps pages the page judge says list the brand; false, pages that do not: by the judge, or a stored copy that never names it. With brandRule not_named, false is the pages to…
pagesstring–all, or third_party: only pages on no brand's own site (not the filter brand's, not any other brand's) and not Parse's own. For a listing pitch, also pass filter.brand and listsBrand: false. Write th…
sortstring–default citations; omitting needs filter.brand
viewstring–pages: pages AI answers cite (search APIs' ranked lists need sign-in)
windowobject–default the last 28 days; "last" or from/to

No output schema declared.

No examples provided.

Install

How do I install the gl.parse/mcp server?

gl.parse/mcp is a hosted endpoint at https://agent.parse.gl/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 · agent.parse.gl

# add to Claude Code
claude mcp add --transport http gl-parse-mcp 'https://agent.parse.gl/mcp'
Common questions

What is the gl.parse/mcp server?

gl.parse/mcp is listed in the public MCP registry as gl.parse/mcp. How ChatGPT and Google AI Mode name, recommend and cite brands. This page covers its hosted endpoint (https://agent.parse.gl/mcp).

Is the gl.parse/mcp server safe to use?

gl.parse/mcp scores 74 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 gl.parse/mcp server expose?

gl.parse/mcp exposes 6 tools: check_brand, resolve_ids, query_metrics, search_answers, search_cited_pages, get_brief. Their descriptions and schemas cost roughly 2,040 tokens of context every time the server is loaded.

Does the gl.parse/mcp server require authentication?

No. We connected to gl.parse/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the gl.parse/mcp server still maintained?

gl.parse/mcp 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 gl.parse/mcp server?

VerifyMCP ran 13 checks on gl.parse/mcp, 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.