check_forges

Ask every connected forge whether its credential still works, the way its method allows, and record the answer on each connection.

Forgewritesnot idempotentMCP tool

A refusal marks the connection as refused until a person connects it again.

Calling it#

curl -X POST http://127.0.0.1:8787/forge.v1.ForgeService/CheckForges \
  -H 'Content-Type: application/json' \
  -d '{}'

komrad rpc check-forges

{
  "name": "check_forges",
  "arguments": {}
}

Offered by the komrad MCP server to orchestrator agents.

No fields.

Field	Type	Description
`checks`	list of ForgeCheck	One entry per connection, in the order list_forges gives them.

Field	Type	Description
`forge`	Forge	The connection.
`problem`	string	What the forge answered, empty when it accepted the credential.
`problemKind`	string	Which kind of trouble it is when problem is set: refused, no_credential or unreachable.

Field	Type	Description
`id`	string	The connection's own id.
`kind`	string	Which forge the host runs, github or gitlab.
`host`	string	The host agents' remotes name, such as github.com.
`apiUrl`	string	Where an enterprise host answers API calls, empty for the public forge.
`method`	string	How the credential was obtained, token or github_app.
`login`	string	Who the forge said the credential belongs to, a user login or an App's name.
`verifiedAt`	string	When the forge last confirmed the credential, in RFC 3339, unset once it refused.
`hasCredential`	bool	Whether this machine still holds what the connection needs to speak, which for a token is its file and for an App is always so.
`createdAt`	string	When the connection was made, in RFC 3339.