Uk Police MCP server
{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-police/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-police/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-police/"
}
}
}{
"servers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-police/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-police/"
}
}
}What it does
This is the MCPBundles Hub, a general-purpose MCP server that aggregates tools from 1,500+ provider integrations (including GitHub, Slack, Notion, Google Drive, Salesforce, Stripe, and others). It is for developers who want to connect multiple third-party services to their AI assistant through a single MCP endpoint, rather than configuring individual servers.
- Execute tools from multiple connected services (GitHub, Slack, Google Drive, etc.) through one MCP interface.
- Search and discover available tools across your enabled bundles to find what is available for your workflow.
- Authenticate once with OAuth or API keys and use credentials automatically for tool execution across different providers.
Tools this server exposes
| Tool | Does |
|---|---|
| execute_tool | Run any tool from your enabled bundles by name and parameters. |
| list_tools | Discover and list all tools available across your connected bundles. |
| search_tools | Search for tools by name, provider, or capability. |
| check_readiness | Verify bundle configuration and credential status before executing tools. |
| get_tool_details | View parameters, descriptions, and usage information for specific tools. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.