Asked Thrice MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Askedthrice bridge for measured brand-recommendation observations: Do provider answers and per-domain observation dates remain attached to reported brand visibility?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Measure whether AI assistants recommend a particular brand across queries.

What we know

Measure whether AI assistants actually recommend a brand, from measured answers. Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Maintenance / activity evidence

askedthrice-mcp 0.1.0 published 2026-08-30T18:47:21.556Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: low.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Brand strategy, Prompt/query corpus

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do provider answers and per-domain observation dates remain attached to reported brand visibility?

The bounded review of the publisher's documented Askedthrice bridge for measured brand-recommendation observations and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
Sensitive access: Brand strategy, Prompt/query corpus
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
writeActions: exact exposed tool mutation authority
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
transport and actual executable entry point
Which providers are polled and whether queries are stored are unverified
Measurement is observational, not guaranteed search-engine rank
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Original activity observations

askedthrice-mcp 0.1.0 published 2026-08-30T18:47:21.556Z

Technical identity

npm/askedthrice-mcp

Exact implementation source: https://www.npmjs.com/package/askedthrice-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:askedthrice-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
askedthrice-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Official remote endpoint or npm stdio; check provider output disclaimers
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Official remote endpoint or npm stdio; check provider output disclaimers | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add --transport http askedthrice https://mcp.askedthrice.com/mcp
Configure / authenticate
MCP100 setup guide
Remote HTTP is publisher documented; local stdio alternative `npx -y askedthrice-mcp`.
Check connection
Suggested check
Confirm askedthrice tools appear in the client.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `askedthrice`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove askedthrice

Official Documentation & Sources

What it does

Measure whether AI assistants actually recommend a brand, from measured answers. Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Capability: Search & Web
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Measure whether AI assistants recommend a particular brand across queries.

Representative uses

Run brand visibility queries
Track citation and recommendation outputs

Limitations

Which providers are polled and whether queries are stored are unverified
Measurement is observational, not guaranteed search-engine rank
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Brand strategy Prompt/query corpus

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The available discovery description lists: Run brand visibility queries; Track citation and recommendation outputs. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Recorded sensitive-access context: Brand strategy; Prompt/query corpus.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. Which providers are polled and whether queries are stored are unverified. Measurement is observational, not guaranteed search-engine rank. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.