Connect Claude to the Agentic QA drop-check service, so it can open a real browser, look a provider up on a carrier's live directory, and tell you whether that provider is still listed.
Make sure you have the following before starting:
claude
command. Other MCP clients can use the configuration in Part B.Give the key a name, such as your organization or team, and create it. The key starts with aqk_.
Open a terminal (not a Claude chat) and run this, with your key in place of <your-api-key>:
claude mcp add --transport http agentic-qa https://agentic-qa.dataweav.com/mcp --header "Authorization: Bearer <your-api-key>"
The address of this server is https://agentic-qa.dataweav.com/mcp.
Restart Claude Code, then type /mcp. You should see agentic-qa listed as connected,
with three tools: list_sites, submit_drop_check and get_drop_check.
Ask Claude in plain language:
The check runs in a real browser and takes a few minutes. Claude will tell you it is running and check back for the result. A made-up name like the second one should come back confirmed absent.
Any client that supports remote MCP servers over HTTP with a custom header can connect with:
{
"mcpServers": {
"agentic-qa": {
"type": "http",
"url": "https://agentic-qa.dataweav.com/mcp",
"headers": { "Authorization": "Bearer <your-api-key>" }
}
}
}
| You see | What it means |
|---|---|
| "Authentication required" | The key is missing or mistyped. Check the Authorization header, or create a new key in Step 1. |
| The site you want isn't in the list | Only sites the team has set up and signed are offered. Ask the team to add it. |
| A message asking for a ZIP code or NPI | Some sites can't be searched without it. Give it to Claude and it will submit again. |
| "Couldn't determine" | The check could not decide, so it does not mean the provider is gone. Read the reason, then ask Claude to run it again. |