claim-verifier
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_urlA | Fetch a URL (following redirects) and report its live status, final URL, page title, and a text snippet. Optionally check that the page contains an expected phrase. Use to verify claims like "the post is live" or "the page says X". |
| verify_githubA | Check the live state of a public GitHub pull request or issue via the GitHub API (state, merged flag, merged_at, title, url). Use to verify claims like "the PR was merged". |
| verify_claimB | Generic claim verifier: one assertion in, a boolean verdict plus the raw evidence out. "contains" checks page text for a phrase, "status_2xx" checks the URL loads successfully, "github_merged" checks a GitHub PR is merged. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
verify_url and verify_claim both verify URL loading and phrase presence, while verify_github and verify_claim both verify GitHub merged state. The generic verify_claim tool overlaps heavily with both specialized tools, making tool selection ambiguous.
All tools follow a strict verify_<target> pattern with clear, predictable nouns. This makes the tool names consistent and easy to guess.
Three tools is a reasonable, focused count for a small claim-verification server. However, verify_claim largely duplicates the other two, so not every tool fully earns its place.
Core URL and GitHub PR/issue verification workflows are covered with useful evidence. The surface is narrow and lacks support for other claim types like API responses or commits, but no obvious dead ends exist for the stated purpose.