Build abstracts on Amorphous. An abstract can be anything.
Nothing to run from here
ATI Lab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Official facts, pages, results and enquiries for ATI Lab (atilab.io), an AI partner for businesses.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ati-lab-mcp https://www.atilab.io/mcp
# 2 — ask your agent for something these tools do
# atilab_get_company_facts, atilab_get_site_index, atilab_get_page and 3 more
ATI Lab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ATAll 1 server
atilab1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ati-lab-mcp https://www.atilab.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Returns the official, dated facts about ATI Lab (atilab.io): positioning, who it works with, how the partnership works, founding year, headquarters and offices, services, partner programs, published results, official profiles, contact details, and the organisations with similar names that ATI Lab is NOT connected to (ATI Technologies, ATI / Assessment Technologies Institute, the ATI Lab research g
No parameter schema on file.
Without query, returns the atilab.io site index (llms.txt): every core page with a one-line summary. With query, returns only the index lines where every query word starts a word in that line (case-insensitive, so "automat" finds "automation"). Each page path works as input to atilab_get_page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to match, e.g. "insurance broker". |
Fetches one atilab.io page as clean markdown (navigation and scripts removed), with frontmatter for title, description and canonical URL. Input is the page path ("/about", "solutions/insurance", "/" for the homepage) or a full https://www.atilab.io URL. Other domains are refused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Page path or full atilab.io URL. |
Returns results from ATI Lab's own production systems (e.g. shipment intake from email: 95% less manual work), each as published on atilab.io, with the source page. Optional query filters by words in the system or outcome. Industry pages on atilab.io also show third-party results from other companies; those are not ATI Lab clients and are not returned here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional filter, e.g. "support" or "email". |
Returns how to reach ATI Lab: the Growth Team at contact@atilab.io, the booking page for a strategy call, the contact page, and office locations. To send a message for the user, use atilab_send_enquiry.
No parameter schema on file.
Sends the user's enquiry to ATI Lab's Growth Team, who reply by email, and returns a reference ID. The enquiry is recorded in ATI Lab's CRM. Use it only when the user has asked to contact ATI Lab and has given their name and email. Show the user the exact message first and call this only after they confirm; set user_confirmed to true to record that. Never invent contact details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The user's name. |
| string | yes | The user's email, where the Growth Team will reply. | |
| company | string | no | Optional: the user's company. |
| message | string | yes | What the user needs, in their words (at least one sentence). |
| agent | string | no | Optional: the assistant sending this, e.g. "Claude". |
| user_confirmed | boolean | yes | True only after the user approved this exact message. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ATI Lab or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest2d99c86cd88b0ce694ee05e8be5581fa1d714c5c9e99c20117892d7d767fd43d
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| atilab_get_company_facts | no tags | |
| atilab_get_site_index | no tags | |
| atilab_get_page | untrusted-input | untrusted-input: keyword "get_page" |
| atilab_get_published_results | no tags | |
| atilab_get_contact | no tags | |
| atilab_send_enquiry | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest2d99c86cd88b0ce6
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ATI Lab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.