← Registry

Developer Tools

semconv.com

An MCP server for searching and looking up OpenTelemetry semantic conventions, specifications, and OTLP releases, including attribute validation and version history.

1 endpoint8 known toolsFirst detected September 27, 2026Last detected September 27, 2026

ENDPOINT 1

https://semconv.com/mcp

No auth detected

MCP server metadata

Name
semconv.com
Version
1.0.0
Capabilities
tools
Server instructions

Read-only access to the OpenTelemetry semantic conventions, specification and OTLP definitions, with their release histories. Reach for check_attribute_names before asserting that an attribute key is current, and search_requirements before asserting what the spec requires - the conventions rename keys every month and a model's training data is usually behind them. Note that the OTLP protocol specification lives in the opentelemetry-proto repository, not the specification one; both are covered.

Known tools 8

search

Search everything semconv.com knows in one call: both attribute registries, metrics, spans, events, entities, every MUST/SHOULD/MAY in the specification and in OTLP, the OTLP wire messages and the domain pages.

Inferred read-only
list_versions

List every tracked release of all three OpenTelemetry sources - semantic conventions, the specification, and OTLP - newest first, with publication dates and how many breaking, notable and editorial changes each one introduced.

Inferred read-only
check_attribute_names

Given attribute keys a codebase emits or queries, report which are deprecated, renamed, moved to another registry, or absent.

Inferred read-only
get_attribute

Full definition of one semantic-conventions attribute: type, stability, guidance note, examples, which signals carry it, and its release-by-release history.

Inferred read-only
search_attributes

Search the semantic-conventions attribute registry by substring against ids and descriptions, optionally narrowed to a namespace or to deprecated entries only.

Inferred read-only
diff_versions

What changed between two tracked versions of one source.

Inferred read-only
search_requirements

Search the RFC 2119 requirements of the OpenTelemetry specification and the OTLP protocol document - the sentences that actually bind an implementation.

Inferred read-only
get_otlp_message

One OTLP wire definition in full: every field with its number, type and cardinality, or every value of an enum.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.semconv-com]
url = "https://semconv.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "semconv-com": {
      "type": "http",
      "url": "https://semconv.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: semconv-com
Remote MCP URL: https://semconv.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "semconv-com": {
      "url": "https://semconv.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "semconv-com": {
      "type": "http",
      "url": "https://semconv.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "semconv-com",
  "transport": "streamable-http",
  "url": "https://semconv.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.