Add A2ABench remote MCP server

[khalidsaidi]

Summary

• add registries/toolhive/servers/a2abench/server.json
• include streamable HTTP remote endpoint (https://a2abench-mcp.web.app/mcp)
• include publisher metadata, tags, and tool list

Notes

• local validation command could not run in this environment because Go toolchain go1.26 is unavailable (toolchain not available).
• entry follows the current remote server JSON pattern used in this catalog.

[JAORMX]

Hey @khalidsaidi, thanks for taking the time to submit A2ABench to the ToolHive catalog! We appreciate the contribution.

So, we took a look at the project against our registry criteria and, to be honest, it's still a bit early for us to include it. The repo currently has 0 stars and 0 forks, which tells us the project hasn't gotten much community traction yet. We generally look for some level of adoption and community engagement before adding servers to the catalog, as that helps us ensure the entries we list are actively maintained and useful to folks.

That said, we'd love to revisit this once the project picks up some momentum! In the meantime, here are a few things to address in the server.json for when you resubmit:

• Missing icon.svg file: Every server directory needs an icon.svg committed alongside server.json. The icons.src field should point to the file in this repo, not an external URL.
• Missing remote tag: Remote servers should include "remote" in their tags list.
• metadata.last_updated: This field is auto-populated by CI, so it shouldn't be set manually. Just remove the metadata block from your entry.
• Namespace: The name field should follow the io.github.stacklok/<server-name> convention used by all existing entries in the catalog.

Note that you can check out our docs for adding entries for the full schema reference.

We're not closing the door on this! Get some traction, address these items, and we'd be happy to take another look. Happy hacking!