Any MCP client

Valency Bond™ is a remote MCP server over streamable HTTP with OAuth. Any client that supports both can connect to it. The platform guides just spell out the same details in each client's own vocabulary.

Connection details

Setting	Value
Server URL	https://mcp.valency.io/
Transport	Streamable HTTP (not SSE, not stdio)
Authentication	OAuth 2.0
Client registration	Dynamic, with no client ID or secret to paste
Client secret / bearer token	Not used. See Direct API for token-based access.

Keep the trailing slash

Some clients build their sign-in callback address from the server URL, so enter it exactly as https://mcp.valency.io/, including the trailing slash. This is what bit the Codex CLI.

Setup

1. Add the server in whatever way your client supports: a UI for adding a remote or custom MCP server, a CLI command, or its configuration file. Most JSON-configured clients want something close to this:

   MCP configuration

   {
     "mcpServers": {
       "valency": {
         "type": "http",
         "url": "https://mcp.valency.io/"
       }
     }
   }

   The exact key names vary by client. Some use httpUrl instead of url, and some nest servers under a different top-level key. Match your client's documented schema; only the URL and the HTTP transport are fixed.

2. Complete the sign-in flow. Valency Bond supports dynamic client registration, so your client registers itself on first connect. You should never be asked for a client ID, client secret, bearer token, or a fixed callback URL.

   Note

   A Valency account is created automatically the first time you sign in. The email you use does not have to match the email on your AI provider account.

3. Confirm the tools loaded. valency should report as connected with the Valency tools (paper search, author lookup, citation lookup, trend analysis, and more) listed: 38 endpoints in all.

4. Ask (more prompt ideas):

   Use Valency to search for papers about quantum computing

You're connected

You see paper results. You can also explicitly invoke Valency tool calls.

Troubleshooting

Client asks for a client ID, secret, or token? It probably isn't using dynamic client registration for this server. Check whether it has a separate "remote" or "OAuth" server type. A client's default MCP entry is often stdio, which can't reach a hosted server.

Sign-in opens but never completes? The callback address your client submitted may not be one Valency accepts. Report the issue and include the client name, version, and the callback URL it used (leave off the query string, which carries the authorization code).

Connects but no tools appear? Restart the client so it picks up the new server connection. If tools still don't appear, confirm the transport is streamable HTTP rather than SSE.

Client doesn't support OAuth at all? Use the Direct API with a bearer token instead.

---

Need help?

If something isn't working, check Troubleshooting for common fixes. See the FAQ for general questions, or report an issue if you're still stuck. Tell us which client you're using and we'll look at adding a guide for it.