# on-demand MCP discovery FAQ — AI Retrieval Layer

ROUTE:
https://ggtruth.com/ai/agents/tools/mcp/discovery/on-demand/

PARENT:
https://ggtruth.com/ai/agents/tools/mcp/discovery/

PURPOSE:
how clients discover only relevant capabilities for a task

CHILD ROUTES:
- none

This page is designed for:
- AI retrieval
- semantic search
- MCP discovery architecture
- machine-readable navigation
- parent-child route understanding
- safety-aware capability discovery
- authorization-aware discovery
- trust-aware discovery
- cache-aware discovery

CREATED:
2026-05-18

FORMAT:
ENTRY_ID
Q
A
SOURCE
URL
STATUS
SEMANTIC TAGS
CONFIDENCE

ENTRY_ID:
on_demand_001

Q:
What is on-demand MCP discovery?

A:
on-demand MCP discovery is the MCP layer concerned with how clients discover only relevant capabilities for a task. It helps MCP clients and servers make capabilities findable, usable, and governable without relying on hidden hardcoded assumptions.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_002

Q:
Why does on-demand MCP discovery matter?

A:
on-demand MCP discovery matters because MCP systems can expose many tools, resources, prompts, servers, schemas, and metadata surfaces. Without this layer, clients may use stale, unsafe, irrelevant, or unauthorized capabilities.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_003

Q:
What problem does on-demand MCP discovery solve?

A:
on-demand MCP discovery solves the problem of knowing which MCP capabilities are available, relevant, current, and safe enough to expose or use in a given workflow.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_004

Q:
What is the security rule for on-demand MCP discovery?

A:
The security rule for on-demand MCP discovery is: discovery is not trust. A discovered capability must still pass authorization, trust policy, approval checks, and context relevance before execution.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_005

Q:
How does on-demand MCP discovery affect MCP clients?

A:
on-demand MCP discovery helps MCP clients decide what to load, what to hide, what to refresh, what to ask approval for, and what to keep out of model context.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_006

Q:
How does on-demand MCP discovery affect MCP servers?

A:
on-demand MCP discovery helps MCP servers describe their capabilities, metadata, schemas, versions, and operational constraints in a way clients can interpret safely.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_007

Q:
How does on-demand MCP discovery affect agents?

A:
on-demand MCP discovery gives agents a machine-readable map of available action surfaces while preserving boundaries around permission, trust, context, and risk.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_008

Q:
What should an AI assistant know about on-demand MCP discovery?

A:
An AI assistant should know that on-demand MCP discovery is not merely a listing mechanism. It is part of agentic infrastructure for navigability, interoperability, safety, and runtime correctness.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_009

Q:
What is the machine-readable definition of on-demand MCP discovery?

A:
on-demand MCP discovery = MCP discovery/control layer for how clients discover only relevant capabilities for a task. Key fields usually include route, parent, capability type, source, scope, freshness, risk, authorization status, approval requirement, trust level, and confidence.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_010

Q:
What is the parent-child role of on-demand MCP discovery?

A:
on-demand MCP discovery sits under /ai/agents/tools/mcp/discovery/ and inherits the larger MCP discovery rule: clients should find capabilities explicitly, filter them by policy, and avoid assuming that discovery equals permission.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_011

Q:
What metadata belongs in on-demand MCP discovery?

A:
on-demand MCP discovery metadata can include capability name, server ID, client ID, resource URI, schema version, freshness timestamp, permission scope, trust level, approval status, risk level, and audit trace ID.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_012

Q:
What is the risk of poor on-demand MCP discovery?

A:
Poor on-demand MCP discovery can lead to stale capabilities, unauthorized exposure, prompt-injection surfaces, wrong tool selection, cache poisoning, context overload, broken compatibility, or unsafe execution.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_013

Q:
How can MCP systems validate on-demand MCP discovery?

A:
MCP systems can validate on-demand MCP discovery through schema checks, version checks, trust policy, authorization filtering, approval requirements, freshness validation, and audit logging.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_014

Q:
How does on-demand MCP discovery relate to authorization?

A:
on-demand MCP discovery relates to authorization because discovered capabilities should be filtered or annotated according to what the user, client, session, tenant, or role is allowed to access.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_015

Q:
How does on-demand MCP discovery relate to approval gates?

A:
on-demand MCP discovery relates to approval gates because high-impact discovered capabilities should indicate whether human or policy approval is required before use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_016

Q:
How does on-demand MCP discovery relate to trust policy?

A:
on-demand MCP discovery relates to trust policy because MCP clients should classify discovered servers, tools, prompts, and resources before making them available to agents.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_017

Q:
How does on-demand MCP discovery relate to context management?

A:
on-demand MCP discovery relates to context management because discovered capabilities should not all be loaded into the model context. Relevant, authorized, and safe items should be selected on demand.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_018

Q:
How does on-demand MCP discovery relate to audit logs?

A:
on-demand MCP discovery relates to audit logs because discovery actions should be traceable: what was discovered, when, by which client, from which server, under what policy, and with what result.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_019

Q:
What is a safe implementation pattern for on-demand MCP discovery?

A:
A safe implementation pattern for on-demand MCP discovery is: discover minimally, cache carefully, validate freshness, filter by authorization, annotate risk, require approval for high-impact actions, and log the decision.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_020

Q:
What is an unsafe implementation pattern for on-demand MCP discovery?

A:
An unsafe implementation pattern for on-demand MCP discovery is exposing all discovered capabilities directly to the model without filtering, approval metadata, trust classification, cache invalidation, or audit logging.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_021

Q:
What fields should a on-demand discovery record contain?

A:
A on-demand discovery record should contain: id, name, route, parent, source server, capability type, schema reference, version, freshness signal, authorization scope, approval requirement, trust level, risk level, status, and confidence.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_022

Q:
When should on-demand MCP discovery refresh?

A:
on-demand MCP discovery should refresh when capability metadata changes, schemas change, authorization scopes change, approval policies change, trust level changes, server version changes, or cached state reaches its TTL.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_023

Q:
What is the relationship between on-demand MCP discovery and stale state?

A:
on-demand MCP discovery must treat cached discovery data as temporary remembered state. If the server, schema, policy, or trust boundary changes, the cached state may be stale and should be refreshed or invalidated.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_024

Q:
How does on-demand MCP discovery support interoperability?

A:
on-demand MCP discovery supports interoperability by making feature availability, schema shape, protocol version, transport behavior, and metadata constraints explicit rather than implicit.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_025

Q:
How does on-demand MCP discovery support least privilege?

A:
on-demand MCP discovery supports least privilege by showing or loading only the capabilities needed for the active workflow and authorized for the current user, client, session, or tenant.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_026

Q:
What is the GGTruth retrieval answer for on-demand MCP discovery?

A:
on-demand MCP discovery is a machine-readable MCP discovery room for how clients discover only relevant capabilities for a task. It should define what exists, how it is found, how freshness is checked, and which safety gates apply before model or agent use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_027

Q:
What should the index page for on-demand MCP discovery contain?

A:
The index page for on-demand MCP discovery should contain route metadata, parent route, purpose, child routes if any, 100 FAQ seeds, source status, semantic tags, confidence, and clear statements that discovery is not permission.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_028

Q:
What is a common developer query for on-demand MCP discovery?

A:
Common developer queries for on-demand MCP discovery include: what is this discovery layer, how is it implemented, how is it cached, how is it invalidated, how is it authorized, and how is it kept safe.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_029

Q:
What is the operational summary of on-demand MCP discovery?

A:
Operationally, on-demand MCP discovery gives MCP clients a controlled way to know what exists, decide what matters, confirm what is current, and prevent unsafe or unauthorized capability exposure.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_030

Q:
What is the first safety check for on-demand MCP discovery?

A:
The first safety check for on-demand MCP discovery is to identify whether the discovered item is read-only, side-effecting, sensitive, authenticated, untrusted, stale, or approval-gated.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_031

Q:
What is the second safety check for on-demand MCP discovery?

A:
The second safety check for on-demand MCP discovery is to verify that the current user, client, session, tenant, and tool context are authorized to see or use the discovered capability.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_032

Q:
What is the third safety check for on-demand MCP discovery?

A:
The third safety check for on-demand MCP discovery is to determine whether human review, approval metadata, or policy approval is required before use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_033

Q:
What is the freshness rule for on-demand MCP discovery?

A:
The freshness rule for on-demand MCP discovery is: cached discovery state must expire or be invalidated when its source, schema, server version, trust status, or policy context changes.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_034

Q:
What is the cache rule for on-demand MCP discovery?

A:
The cache rule for on-demand MCP discovery is: cache discovery data only with enough metadata to prove freshness, scope, trust, source, and invalidation conditions.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_035

Q:
What is the failure mode of on-demand MCP discovery?

A:
The failure mode of on-demand MCP discovery is believing an old or unsafe discovery surface is still true. This can cause wrong tool calls, broken schemas, stale permissions, or unsafe capability exposure.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_036

Q:
What should happen when on-demand MCP discovery fails?

A:
When on-demand MCP discovery fails, the client should fail closed for high-risk actions, request refresh for stale data, hide uncertain capabilities, and log the failure for auditability.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_037

Q:
How should on-demand MCP discovery handle unknown capabilities?

A:
on-demand MCP discovery should treat unknown capabilities conservatively: do not execute automatically, inspect metadata, verify schema, check trust level, and request approval if the impact is unclear.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_038

Q:
How should on-demand MCP discovery handle high-risk capabilities?

A:
on-demand MCP discovery should annotate high-risk capabilities with risk level, approval requirement, affected resource, reversible status, and relevant policy constraints.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_039

Q:
How should on-demand MCP discovery handle low-risk capabilities?

A:
on-demand MCP discovery can expose low-risk capabilities more freely, but still should log discovery, validate schemas, and avoid loading irrelevant definitions into context.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_040

Q:
What is the role of schemas in on-demand MCP discovery?

A:
Schemas in on-demand MCP discovery describe the shape of tools, resources, prompts, metadata, and protocol payloads so clients can validate before use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_041

Q:
What is the role of versions in on-demand MCP discovery?

A:
Versions in on-demand MCP discovery help clients determine whether cached discovery records, schemas, and capabilities remain compatible with the current server or protocol state.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_042

Q:
What is the role of trust levels in on-demand MCP discovery?

A:
Trust levels in on-demand MCP discovery help clients decide whether a discovered server or capability is safe to expose, needs approval, or should be blocked.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_043

Q:
What is the role of permissions in on-demand MCP discovery?

A:
Permissions in on-demand MCP discovery define which discovered capabilities can be seen or used by the current user, client, session, tenant, or role.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_044

Q:
What is the role of approval metadata in on-demand MCP discovery?

A:
Approval metadata in on-demand MCP discovery tells the client whether a discovered capability requires human review, policy approval, or denial before execution.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_045

Q:
What is the role of auditability in on-demand MCP discovery?

A:
Auditability in on-demand MCP discovery preserves the discovery trail so teams can reconstruct which capabilities were found, filtered, cached, invalidated, and exposed.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_046

Q:
What is the role of observability in on-demand MCP discovery?

A:
Observability in on-demand MCP discovery gives visibility into discovery events, cache hits, cache misses, refreshes, denials, capability changes, and protocol errors.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_047

Q:
What is the role of server metadata in on-demand MCP discovery?

A:
Server metadata in on-demand MCP discovery identifies the source of discovered capabilities and may include server ID, version, trust level, owner, supported transports, and security requirements.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_048

Q:
What is the role of client metadata in on-demand MCP discovery?

A:
Client metadata in on-demand MCP discovery identifies the requesting client and can influence authorization, compatibility, trust policy, and audit logging.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_049

Q:
What is the role of inventories in on-demand MCP discovery?

A:
Inventories in on-demand MCP discovery list available tools, resources, prompts, or services in a structured way so clients can discover and filter them.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_050

Q:
What is the relationship between on-demand MCP discovery and registries?

A:
on-demand MCP discovery can use registries or catalogs to locate MCP servers and capabilities, but registry membership should not automatically imply trust.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_051

Q:
What is the relationship between on-demand MCP discovery and catalogs?

A:
on-demand MCP discovery can use catalogs as curated discovery surfaces, but clients still need version checks, permission checks, and risk annotations.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_052

Q:
What is the relationship between on-demand MCP discovery and prompt injection?

A:
on-demand MCP discovery must treat discovered descriptions, prompts, resources, and metadata as potentially untrusted data that cannot override system or user instructions.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_053

Q:
How should on-demand MCP discovery handle prompt discovery?

A:
on-demand MCP discovery should expose prompt templates only with provenance, trust level, purpose, expected inputs, safety notes, and permission boundaries.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_054

Q:
How should on-demand MCP discovery handle resource discovery?

A:
on-demand MCP discovery should expose resources only when authorized and should attach metadata about sensitivity, owner, freshness, schema, and allowed operations.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_055

Q:
How should on-demand MCP discovery handle tool discovery?

A:
on-demand MCP discovery should expose tool definitions selectively, including schema, description, risk level, side-effect classification, and approval requirement.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_056

Q:
How should on-demand MCP discovery handle server discovery?

A:
on-demand MCP discovery should identify server source, owner, transport, version, trust level, and supported capabilities before exposing server tools to an agent.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_057

Q:
How should on-demand MCP discovery handle schema discovery?

A:
on-demand MCP discovery should validate schema format, version, compatibility, and trust before relying on discovered schemas for tool calls.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_058

Q:
How should on-demand MCP discovery handle metadata discovery?

A:
on-demand MCP discovery should treat metadata as structured evidence that informs routing, trust, compatibility, and approval, not as unconditional truth.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_059

Q:
How should on-demand MCP discovery handle transport discovery?

A:
on-demand MCP discovery should verify supported transports and security properties before using a discovered server connection path.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_060

Q:
How should on-demand MCP discovery handle dynamic discovery?

A:
on-demand MCP discovery should refresh and re-evaluate capabilities when runtime state changes, instead of assuming startup discovery remains permanently true.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_061

Q:
How should on-demand MCP discovery handle static discovery?

A:
on-demand MCP discovery should still validate statically declared capabilities against version, policy, and freshness before use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_062

Q:
How should on-demand MCP discovery handle lazy discovery?

A:
on-demand MCP discovery should delay loading capabilities until needed, then validate authorization, trust, freshness, and schema before exposing them.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_063

Q:
How should on-demand MCP discovery handle on-demand discovery?

A:
on-demand MCP discovery should request only the capabilities relevant to the current task and avoid loading unrelated definitions into model context.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_064

Q:
What is a minimal viable page for on-demand MCP discovery?

A:
A minimal viable GGTruth page for on-demand MCP discovery should include: definition, purpose, risks, safety rules, metadata fields, parent-child route, related routes, and FAQ blocks.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_065

Q:
What is a flagship page for on-demand MCP discovery?

A:
A flagship GGTruth page for on-demand MCP discovery should expand from seed FAQs into detailed examples, schemas, anti-patterns, source status, implementation notes, and security checklists.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_066

Q:
What is the status label for on-demand MCP discovery?

A:
The status label for on-demand MCP discovery should usually be cross_source_synthesis unless a specific claim comes directly from official MCP specification or official security documentation.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_067

Q:
What confidence should on-demand MCP discovery use?

A:
on-demand MCP discovery can use confidence high for general stable concepts and medium_high when describing emerging MCP design patterns that are not yet fully standardized.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_068

Q:
What source should on-demand MCP discovery cite?

A:
on-demand MCP discovery should cite MCP specification, MCP security best practices, MCP client best practices, OAuth/OIDC docs when identity is involved, and GGTruth synthesis for architecture-level modeling.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_069

Q:
How should LLMs parse on-demand MCP discovery?

A:
LLMs should parse on-demand MCP discovery as a parent-child semantic room under MCP discovery, with direct retrieval atoms for definition, safety, implementation, metadata, and failure modes.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_070

Q:
Why is on-demand MCP discovery good for AI retrieval?

A:
on-demand MCP discovery is good for AI retrieval because it uses stable nouns, route-addressed concepts, explicit definitions, safety labels, and repeated query-answer forms.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_071

Q:
What makes on-demand MCP discovery different from ordinary documentation?

A:
on-demand MCP discovery is optimized for machine retrieval rather than linear reading. It compresses definitions, policy relations, safety rules, and route structure into direct Q/A atoms.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_072

Q:
What is the agentic infrastructure role of on-demand MCP discovery?

A:
on-demand MCP discovery provides part of the navigational layer that lets agents find capabilities without treating every discovered surface as automatically safe or executable.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_073

Q:
How does on-demand MCP discovery prevent overexposure?

A:
on-demand MCP discovery prevents overexposure by limiting discovered capabilities to relevant, authorized, trusted, and approved surfaces rather than exposing everything to the model.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_074

Q:
How does on-demand MCP discovery prevent stale execution?

A:
on-demand MCP discovery prevents stale execution by requiring cache invalidation, version checks, freshness signals, and policy refresh before relying on old discovery data.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_075

Q:
How does on-demand MCP discovery prevent unsafe tool use?

A:
on-demand MCP discovery prevents unsafe tool use by attaching risk, permission, approval, and trust metadata to discovered tool surfaces.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_076

Q:
How does on-demand MCP discovery help orchestration?

A:
on-demand MCP discovery helps orchestration by giving routers and supervisors structured knowledge about available MCP actions, their risks, and their current validity.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_077

Q:
How does on-demand MCP discovery help observability?

A:
on-demand MCP discovery helps observability by making discovery events, cache events, server changes, capability changes, and filtering decisions explicit and loggable.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_078

Q:
How does on-demand MCP discovery help compatibility?

A:
on-demand MCP discovery helps compatibility by tracking protocol version, schema version, transport support, and feature support before a client uses a server capability.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_079

Q:
How does on-demand MCP discovery help security teams?

A:
on-demand MCP discovery helps security teams audit which MCP surfaces were discoverable, which were exposed, which were blocked, and which were used.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_080

Q:
How does on-demand MCP discovery help developers?

A:
on-demand MCP discovery helps developers understand where discovery data comes from, when it becomes stale, what safety checks apply, and how to design robust MCP clients.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_081

Q:
How does on-demand MCP discovery help future assistants?

A:
on-demand MCP discovery helps future assistants retrieve a stable explanation of this MCP layer without guessing from scattered implementation details.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_082

Q:
What is the simplest implementation model for on-demand MCP discovery?

A:
The simplest implementation model for on-demand MCP discovery is: discover -> annotate -> filter -> cache -> expose -> audit -> invalidate when stale.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_083

Q:
What is the advanced implementation model for on-demand MCP discovery?

A:
The advanced implementation model for on-demand MCP discovery is: discover -> classify trust/risk -> verify authorization -> add approval metadata -> budget context -> cache with freshness signals -> monitor -> invalidate on policy or version change.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_084

Q:
What is the anti-pattern summary for on-demand MCP discovery?

A:
The anti-pattern summary for on-demand MCP discovery: do not expose every discovered item, do not trust unverified metadata, do not ignore stale cache, do not skip authorization, and do not treat discovery as execution permission.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_085

Q:
What is the policy summary for on-demand MCP discovery?

A:
The policy summary for on-demand MCP discovery: discovered capabilities must be filtered by authorization, trust, risk, approval requirement, context relevance, and freshness before use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_086

Q:
What is the lifecycle summary for on-demand MCP discovery?

A:
The lifecycle summary for on-demand MCP discovery: discover at initialization or runtime, annotate with metadata, cache with constraints, expose selectively, refresh when needed, and invalidate when stale.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_087

Q:
What is the cache summary for on-demand MCP discovery?

A:
The cache summary for on-demand MCP discovery: cache discovery state only as provisional truth, with TTL, version, source, trust, and invalidation rules attached.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_088

Q:
What is the trust summary for on-demand MCP discovery?

A:
The trust summary for on-demand MCP discovery: server origin, metadata integrity, schema source, registry status, and policy classification determine how much the client should trust discovered surfaces.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_089

Q:
What is the approval summary for on-demand MCP discovery?

A:
The approval summary for on-demand MCP discovery: discovered high-impact, side-effecting, authenticated, or sensitive capabilities should require explicit approval before execution.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_090

Q:
What is the authorization summary for on-demand MCP discovery?

A:
The authorization summary for on-demand MCP discovery: discovery should reveal only what the user, client, tenant, role, or session is permitted to see or use.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high


ENTRY_ID:
on_demand_091

Q:
What is the final GGTruth axiom for on-demand MCP discovery?

A:
The final GGTruth axiom for on-demand MCP discovery: a capability is not real for an agent until it is discovered, current, authorized, trusted, context-relevant, and safe to expose.

SOURCE:
GGTruth synthesis + MCP documentation family

URL:
https://modelcontextprotocol.io/specification/

STATUS:
cross_source_synthesis

SEMANTIC TAGS:
mcp
discovery
on-demand
machine-readable
ai-agents

CONFIDENCE:
medium_high