AWS Bedrock AgentCore vs Agent Daily
AWS Bedrock AgentCore is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Agent Daily is an MCP server published by gregpunch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  AWS Bedrock AgentCore |  Agent Daily |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:df610a7a056f Forks (GitHub): 1 857 Pulls (Docker Hub): 21 148 Stars (Docker Hub): 0 Stars (GitHub): 9 892 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | AWS Bedrock AgentCore | Agent Daily |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 892 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 21 148 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 857 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | On your machine (mcp/amazon-bedrock-agentcore-mcp-server) | Remote server (agent-daily.agentdaily.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 122 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/gregpunch/agent-daily |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-23 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 45 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
AWS Bedrock AgentCore
Documentation on AgentCore platform services.
Agent Daily
Live health of 65 agent APIs/MCPs plus a 15-min LLM leaderboard; recommend(task) picks a provider.
How to run each
AWS Bedrock AgentCore As a local MCP server: Docker image
claude mcp add --transport stdio amazon-bedrock-agentcore -- docker run -i --rm mcp/amazon-bedrock-agentcore-mcp-serverAgent Daily As a remote MCP server
claude mcp add --transport http agent-daily https://agent-daily.agentdaily.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Agent Daily has a remote endpoint we check. How we check endpoints
Tools each declares
Only AWS Bedrock AgentCore has
browser_clickbrowser_closebrowser_console_messagesbrowser_evaluatebrowser_fill_formbrowser_handle_dialogbrowser_hoverbrowser_mouse_wheelbrowser_navigatebrowser_navigate_backbrowser_navigate_forwardbrowser_network_requests
Show the remaining 110
browser_press_keybrowser_resizebrowser_select_optionbrowser_snapshotbrowser_tabsbrowser_take_screenshotbrowser_typebrowser_upload_filebrowser_wait_forcreate_agent_runtimecreate_agent_runtime_endpointdelete_agent_runtimedelete_agent_runtime_endpointdownload_fileexecute_codeexecute_commandfetch_agentcore_docgateway_creategateway_deletegateway_getgateway_listgateway_resource_policy_deletegateway_resource_policy_getgateway_resource_policy_putgateway_target_creategateway_target_deletegateway_target_getgateway_target_listgateway_target_synchronizegateway_target_updategateway_updateget_agent_runtimeget_agent_runtime_endpointget_browser_sessionget_code_interpreter_sessionget_gateway_guideget_identity_guideget_memory_guideget_policy_guideget_runtime_guideidentity_create_api_key_provideridentity_create_oauth2_provideridentity_create_workload_identityidentity_delete_api_key_provideridentity_delete_oauth2_provideridentity_delete_resource_policyidentity_delete_workload_identityidentity_get_api_key_provideridentity_get_oauth2_provideridentity_get_resource_policyidentity_get_token_vaultidentity_get_workload_identityidentity_list_api_key_providersidentity_list_oauth2_providersidentity_list_workload_identitiesidentity_put_resource_policyidentity_set_token_vault_cmkidentity_update_api_key_provideridentity_update_oauth2_provideridentity_update_workload_identityinstall_packagesinvoke_agent_runtimelist_agent_runtime_endpointslist_agent_runtime_versionslist_agent_runtimeslist_browser_sessionslist_code_interpreter_sessionsmemory_batch_create_recordsmemory_batch_delete_recordsmemory_batch_update_recordsmemory_creatememory_create_eventmemory_deletememory_delete_eventmemory_delete_recordmemory_getmemory_get_eventmemory_get_recordmemory_listmemory_list_actorsmemory_list_eventsmemory_list_extraction_jobsmemory_list_recordsmemory_list_sessionsmemory_retrieve_recordsmemory_start_extraction_jobmemory_updatepolicy_createpolicy_deletepolicy_engine_createpolicy_engine_deletepolicy_engine_getpolicy_engine_listpolicy_engine_updatepolicy_generation_getpolicy_generation_listpolicy_generation_list_assetspolicy_generation_startpolicy_getpolicy_listpolicy_updatesearch_agentcore_docsstart_browser_sessionstart_code_interpreter_sessionstop_browser_sessionstop_code_interpreter_sessionstop_runtime_sessionupdate_agent_runtimeupdate_agent_runtime_endpointupload_file
Only Agent Daily has
incidentslist_toolsllm_leaderboardrecommendtool_status
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Agent Daily as of 2026-11-09). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: AWS Bedrock AgentCore · What it can do: Agent Daily · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.