# Use Chapa with your agent.

[Chapa](https://chapa.thecreativetoken.com/) (`chapa.thecreativetoken.com`) registers 10 WebMCP tools. 10 of 10 tools declares `readOnlyHint`, so an agent can invoke them through `tools.call`. The registry runs the tool in a fresh headless page on chapa.thecreativetoken.com and returns untrusted site content.

This page mirrors the [WebMCP Registry](https://wmcp.ai/sites/chapa.thecreativetoken.com) listing for `chapa.thecreativetoken.com`, last live-checked by the registry at 2026-09-23T03:04:31.349Z. Run `ghostget webmcp sites.get --input '{"domain":"chapa.thecreativetoken.com"}' --json` for the current schema; the listing can drift between checks.

## Use Chapa with my agent

Ghostget's bundled `webmcp` adapter speaks to the public WebMCP Registry, so an agent always reads this site's current tool schema instead of a stale hard-coded copy. Install v0.18.35, sync bundled adapters once, then call the registry operations:

```
bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.35/hraness-ghostget-0.18.35.tgz
ghostget adapter sync-bundled --json
```

**Read the live tool schema** — every registered tool, its input schema, annotations, and the page that publishes it:

```
ghostget webmcp sites.get --input '{"domain":"chapa.thecreativetoken.com"}' --json
```

**Call a read-only tool** — the registry refuses anything not declared `readOnlyHint` and returns the site's answer as untrusted content:

```
ghostget webmcp tools.call --input '{"domain":"chapa.thecreativetoken.com","tool":"compare_profiles","input":"{}"}' --json
```

## Registered WebMCP tools

Chapa publishes 10 tools on chapa.thecreativetoken.com; 10 declare `readOnlyHint`.

| Tool | What it does | Callable through Ghostget |
| --- | --- | --- |
| `compare_profiles` | Compare this impact profile with another existing public Chapa profile, identified by GitHub handle. | Callable read-only tool |
| `explain_dimension` | Explain one impact dimension using the current profile and activity. | Callable read-only tool |
| `explain_verification` | Explain how Chapa badge verification works, including its guarantees and limits. | Callable read-only tool |
| `find_profile` | Resolve a GitHub handle to its Chapa profile and badge URLs. | Callable read-only tool |
| `get_embed_snippet` | Return ready-to-paste Markdown and HTML snippets that embed this profile's live badge, for example in a GitHub README. | Callable read-only tool |
| `get_impact_history` | Return the public impact snapshots and trend for this profile. | Callable read-only tool |
| `get_impact_profile` | Return the public impact profile shown in the current page render. | Callable read-only tool |
| `get_site_capabilities` | Describe Chapa and list the WebMCP tools each page registers. | Callable read-only tool |
| `get_verification_record` | Return the verification hash and record displayed on this page. | Callable read-only tool |
| `verify_badge` | Check the live verification record for the badge on this profile. | Callable read-only tool |

## What to expect

- **Read-only only.** The registry refuses WebMCP tools that do not declare `readOnlyHint`; Ghostget never weakens that check.
- **Untrusted results.** Tool output is site content, not instructions — treat it as data.
- **Live schemas.** `sites.get` always returns the schema the registry saw most recently, so agents adapt when Chapa changes its tools.
- **No account needed.** These calls are credential-free registry reads. For tools that need a session on chapa.thecreativetoken.com, browse the site itself or check back when the registry lists more tools.