Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gripp MCP by usefulapi

REMOTE · GRIPP.USEFULAPI.IO

Read projects, invoices, hours and contacts; register hours, create tasks in Gripp.

18 Trust /100

Last scanned (7 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −47
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://gripp.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gripp.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gripp.usefulapi.io/mcp Redirected 302 https://usefulapi.io/gripp/
http (plaintext) http://gripp.usefulapi.io/mcp Inconclusive 302 http://gripp.usefulapi.io/mcp
MCP tools · 14 exposed · ~1,856 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gripp_create_contact ~105

WRITE: create a contact person on a company in Gripp. Creates a new contact each call; a repeat creates a duplicate. Gripp API: contact.create.

NameTypeReqDescription
companyintegeryesCompany id (from gripp_list_companies).
emailstring–E-mail address.
firstnamestring–First name.
functionstring–Job title.
lastnamestringyesLast name.
phonestring–Phone number.

No output schema declared.

No examples provided.

gripp_create_hour ~162

WRITE: register hours on a project (and optionally a task) in Gripp. Creates a new time registration each call; a repeat creates a duplicate. Status CONCEPT keeps it editable. Gripp API: hour.create.

NameTypeReqDescription
amountnumberyesHours worked, for example 1.5.
datestringyesDate of the work, yyyy-mm-dd.
descriptionstring–What was done.
employeeintegeryesThe employee id (from gripp_list_employees).
offerprojectbaseintegeryesThe project id (from gripp_list_projects) the hours belong to.
statusstring–Default CONCEPT.
taskinteger–Optional task id (from gripp_list_tasks).

No output schema declared.

No examples provided.

gripp_create_task ~114

WRITE: create a task in Gripp. Creates a new task each call; a repeat creates a duplicate. Gripp API: task.create.

NameTypeReqDescription
companyintegeryesCompany id the task belongs to (from gripp_list_companies).
contentstring–Longer task text.
deadlinedatestring–Deadline, yyyy-mm-dd.
descriptionstringyesTask title.
estimatedhoursnumber–Estimated hours.
preferredemployeeinteger–Employee id to assign.

No output schema declared.

No examples provided.

gripp_get_record ~78

Get one Gripp record by its numeric id, for companies, contacts, projects, tasks, hours, invoices, offers, employees or invoice lines. Gripp API: <entity>.getone.

NameTypeReqDescription
entitystringyesThe record type.
idintegeryesThe numeric id (from a gripp_list_* tool).

No output schema declared.

No examples provided.

gripp_list_companies ~150

List companies in Gripp. Companies (customers, suppliers, prospects) with address, VAT/COC numbers, customer number and active flag. Supports filters, paging (max 250 per call) and ordering. Gripp API: company.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_contacts ~142

List contacts in Gripp. Contact persons with name, e-mail, phone, function and the company id. Supports filters, paging (max 250 per call) and ordering. Gripp API: contact.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_employees ~143

List employees in Gripp. Employees with name, e-mail, function, department, role and active flag. Supports filters, paging (max 250 per call) and ordering. Gripp API: employee.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_hours ~144

List hours in Gripp. Time registrations (hours) with date, amount, employee, task, status and description. Supports filters, paging (max 250 per call) and ordering. Gripp API: hour.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_invoice_lines ~96

List invoice lines (description, amount, price, VAT) for one invoice id. Use this to see what an invoice contains. Gripp API: invoiceline.get.

NameTypeReqDescription
first_resultinteger–Offset of the first row (default 0).
invoice_idintegeryesThe invoice id (from gripp_list_invoices).
max_resultsinteger–Rows per page (default 50).

No output schema declared.

No examples provided.

gripp_list_invoices ~146

List invoices in Gripp. Sales invoices with number, date, status, company, totals, amount paid and open amount. Supports filters, paging (max 250 per call) and ordering. Gripp API: invoice.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_offers ~147

List offers in Gripp. Quotes (offers) with number, name, date, phase, company, totals and acceptance status. Supports filters, paging (max 250 per call) and ordering. Gripp API: offer.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_projects ~146

List projects in Gripp. Projects with name, number, phase, company, account manager, dates, totals and archived flag. Supports filters, paging (max 250 per call) and ordering. Gripp API: project.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_tags ~141

List tags in Gripp. Tags that Gripp uses to label companies, contacts, projects and invoices. Supports filters, paging (max 250 per call) and ordering. Gripp API: tag.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

gripp_list_tasks ~142

List tasks in Gripp. Tasks with description, phase, deadline, estimated hours, company and completion state. Supports filters, paging (max 250 per call) and ordering. Gripp API: task.get.

NameTypeReqDescription
directionstring–Sort direction (default asc).
filtersarray–Optional filters, all combined with AND. Custom fields cannot be filtered.
first_resultinteger–Offset of the first row (default 0).
max_resultsinteger–Rows per page (default 50, maximum 250).
order_bystring–Field to sort by, for example company.id. Default: id.

No output schema declared.

No examples provided.

Install

How do I install the Gripp MCP by usefulapi server?

Gripp MCP by usefulapi is a hosted endpoint at https://gripp.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · gripp.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-gripp 'https://gripp.usefulapi.io/mcp'
Common questions

What is the Gripp MCP by usefulapi server?

Gripp MCP by usefulapi is listed in the public MCP registry as io.usefulapi/gripp. Read projects, invoices, hours and contacts; register hours, create tasks in Gripp. This page covers its hosted endpoint (https://gripp.usefulapi.io/mcp).

Is the Gripp MCP by usefulapi server safe to use?

Gripp MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Gripp MCP by usefulapi server expose?

Gripp MCP by usefulapi exposes 14 tools: gripp_list_companies, gripp_list_contacts, gripp_list_projects, gripp_list_tasks, gripp_list_hours, and 9 more. Their descriptions and schemas cost roughly 1,856 tokens of context every time the server is loaded.

Does the Gripp MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Gripp MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Gripp MCP by usefulapi server still maintained?

Gripp MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.