Ground agents in verifiable Bluetooth SIG manufacturer records so device and hardware answers rest on the real assigned-identifier registry, not guesses.
Give an agent Bluetooth Company so it resolves and checks hosts against real data before acting, rather than assuming — grounding network reasoning in fact.
Wire bluetoothlookup into an operations agent so its answers about connectivity and infrastructure rest on live lookups it can cite.
Each result the agent relies on carries Bluetooth Company as its source, keeping the reasoning auditable.
Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp",
"headers": { "x-api-key": "vc_live_••••" }
}
}
}Each call returns structured fields your agent can read — and trace back to this source.
companyIdcompanyIdHexfoundcompanyHow to ground an agent in it over MCP.
