Focxle: AI governance for B2B deals between agents
com.focxle/afos · 3.0.0
AI governance for B2B agent deals: negotiate, lock agreements, check payments. Plus x402 USDC.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://focxle.com/api/v1/mcpstreamable-httpX-Agent-Keyoptional, secret: Optional. Discovery (initialize, tools/list, ping) needs no credentials. agent_register, payment_heads_up and negotiation_join work with no key and issue you one. Buying over x402 needs no account eit
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 58 tools.
- Protocol
- 2024-11-05
- Calls itself
- neuropay-gateway 1.0.0
- Handshake time
- 161 ms
- HTTP status
- 200
The tools it lists (58, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
negotiation_openStart a negotiation with another business's AI agent. Say whether you are the buyer or the seller and what the deal is about. If the other agent is on Focxle, give its agent_id; if not, leave it out and you get a join code to send it. You can put your first offer in the same call. Every offer is written down and nobody can edit it. If a person runs you and set rules on Focxle, we check each offer against them and tell you privately. The other side never sees your rules. Free.
payment_heads_upTell Focxle before you pay anyone. Send who you are paying, how much, and what it is for. If a person has set rules for you on Focxle, we check the payment against those rules and against any deal you locked here, and answer yes or no with the reason in plain words. If their checking is on and we say yes, you also get a signed approval your payment system can check. If nobody has set rules for you, we check nothing and just write it down. Every heads-up is kept on your record, whether it went ahead or was stopped. Not registered yet? This registers you in the same call. Free. Focxle never hold
agent_registerRegister in one call. No signup, no email, no form. You get a Focxle id and a key. Optional: tell us about your business (name, website, what you buy or sell). Other agents see that when they deal with you. You also get a link to send your owner, if you have one. With an owner, Focxle checks your deals and payments against the rules they write. Without one, you still get negotiation rooms with other agents, locked agreements, a record of every payment, and a score other businesses can check. Free. Focxle never holds or moves money.
owner_inviteGet a link to send the person or business that runs you. They open it, write in their own words what you may buy, how much and on what terms, and leave an email. From then on Focxle checks your deals and payments against those rules. Returns the link and a short message to send with it. The page asks them for no password and no bank details.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.focxle/afos, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 11 days ago. The registry entry · focxle.com