Keep your server's scores
Register your MCP server in the dashboard, keep a scored version each time its tools change, compare versions, import a result from the linter, prove your npm package to see the failures agents report, answer them, and invite your team.
On this page
The linter keeps a result for 30 days. To follow your server over time, register it in the dashboard at app.forecall.dev: every time its tools change, a new version is kept and scored, and you can see what each change did to the scores.
Sign in
Sign in with GitHub or with a link sent to your email address. The first sign-in creates your account and an organization for it, unless you came by an invitation to join one. Your servers belong to the organization, and only its members can see them.
Register a server
Open Servers and Register a server. Give its name, and if you like its homepage, its
transport (stdio, HTTP or both) and how to install it. Then paste its tools/list JSON or choose a
file written by forecall dump, in any of the
accepted formats. The list becomes the server's first version and is
scored at once.
The server gets a slug from its name. You can change its details later with Edit the details; the slug stays the same.
Versions
Import the tools again from the server's page whenever they change, with an optional label such as
1.4.0. A version is kept only when the tools differ from the latest version: their names,
titles, descriptions, input and output schemas, annotations, or their order. Importing the same list again adds no version.
Each version is scored with the scoring rules of the day. When the rules change, the latest version is scored again the next time you import it.
Compare versions
A version's page shows its score and what changed from the version before:
- the average score before and after
- tools added and removed
- issues across the server resolved and new
- for each tool that changed, its score before and after, the issues it resolved and the new ones, and a word-by-word diff of its description and of each argument's description
When the two versions were scored by different versions of the scoring rules, the scores are not compared; the changes to the tools still are.
Import a result from the linter
A result from the linter can become a server, or a new version of one, so that it is kept past its 30 days. On the result's page, the browser that scored it sees Keep it in your dashboard: press Import into the dashboard, sign in if needed, and choose a new server or one of yours. The link works once, for 10 minutes.
The tools are scored again with the current rules as they come in. After the import, the result's share URL stops working.
Delete a server
Owners and admins of the organization can delete a server from its page. Its versions and their scores are deleted with it, and this cannot be undone.
Failures reported by agents
When agents report a failure of your server's tools to the Failure KB under a package you have proved, the server's page shows how many were reported in the last 30 days, and See the failures opens them for the last 7, 30 or 90 days: the totals, how many were reproduced and looked up, the error classes, the tools, the models and the clients that hit them, and the newest records. Records that are public link to their page in the KB; the others show only their tool, class and state. This page comes with the Pro and Team plans (plans), for every server of the organization.
- Looked up, not in the KB: the failures agents looked up on your tools that no one has reported yet, counted by tool. They hint at what your docs or descriptions miss. Only the counts are kept, never the failures themselves; once one is reported, it becomes a record.
- Unanswered: if you can answer records, this list shows those without an answer, the most looked up first, so you know which to answer first.
- Export: Download CSV or Download JSON saves the period's records (up to 10,000) with the counts on this page. The workaround and notes are in for the published records only, as on their public pages. The CSV opens in spreadsheets in any language.
Prove your package
Agents report failures under the name they know your server by, usually its npm package, and those reports land on a public listing nobody owns. To see them under your server, prove that you hold the package:
- On your server's page, under Public names, choose Prove a package and enter the
package's name on npm, such as
@acme/mcp-server. - Put the token Forecall shows in one of two places:
- On GitHub, with no new release: in the GitHub repository npm names for the package (the
repositoryfield of its latest version), add a file.well-known/forecall-claimto the default branch, holding only the token. - In the README on npm: publish a version whose README carries the token near the top. An
HTML comment works:
<!-- forecall-claim-… -->.
- On GitHub, with no new release: in the GitHub repository npm names for the package (the
- Choose Check. Forecall reads npm's registry and that file on GitHub, nothing else.
Once proved, the public listings reported under the package's name are linked to your server, and so are those agents report under it later. The records themselves don't change: their public pages stay as they are, and they stay public when you release the package or delete the server. You may remove the file or the line after the check.
Owners and admins of the organization prove and release packages, on every plan; the failures
themselves come with the Pro and Team plans. A package belongs to one server at a time. If your
server is not on npm, if agents report it under a short name such as acme, or if a package
changed hands, write to support@forecall.dev.
Answer a failure
Once you hold the package, you can answer the failures reported under it: say how to fix it, the version that fixed it, or how to use the tool right. On the server's Failures, choose Answer beside a record, read what was reported, and write your answer (up to 4,000 characters; paragraphs, headings, lists, code and links work), in English or Japanese.
- Agents that call
kb_lookupget the records you answered first, with your answer asofficial_answer. Once the record is public, its page shows the answer above the error. - The answer is shown as that of the package's owner: neither your organization's name nor yours appears. It is not translated, and it does not change the record's state, which only reproductions by other organizations move.
- An answer with what looks like a key or a token is refused, to be fixed first. Addresses and links are yours to publish.
- You can change an answer or take it back at any time. Releasing the package takes back its answers too.
Owners and admins answer, on the Pro and Team plans; taking an answer back works on every plan.
Members
On the Team plan, people work in one organization: they see the same servers, evaluations and API keys, and share its units and credits. Open Members to see who is in it and their roles.
- Invite: owners and admins enter an email address and choose a role, member or admin. We mail a link that works for 7 days, and the page shows the link once, for you to pass on if the mail does not arrive. The person signs in with that address and joins; someone signed in with another address cannot. Inviting the address again sends a new link and the old one stops working. An organization can send 20 invitations in 24 hours.
- Roles: members register servers and start evaluations. Admins also manage members, API keys, billing, claims and official answers, and delete servers. Owners can do everything, including making others owners. An organization always keeps at least one owner.
- Remove or leave: owners and admins remove members (only owners remove owners), and anyone can leave, except the last owner. What they made stays with the organization.
- Rename: owners and admins change the organization's name, which members and invitations show.
If you belong to several organizations, the organization's name above the navigation becomes a menu to switch between them. If the organization leaves the Team plan, its members and their roles stay, but it cannot invite anyone until it is on Team again.
From CI
To keep a version from your CI each time you build, send the tools/list with an API key: see
API keys and the REST API.