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.

IG Digital Lab, Sacramento, CA

REMOTE · IGDIGI.COM · SCANNED SEP 26

IG Digital Lab, Sacramento, CA: independent software & AI automation agency.

Available components

+3 this week 74 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 525 tokens (~105/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_contact_request" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the IG Digital Lab, Sacramento, CA MCP server?

IG Digital Lab, Sacramento, CA is a hosted endpoint at https://igdigi.com/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 · igdigi.com

# add to Claude Code
claude mcp add --transport http com-igdigi-igdigi 'https://igdigi.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-igdigi-igdigi": {
      "url": "https://igdigi.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-igdigi-igdigi": {
      "type": "http",
      "url": "https://igdigi.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-igdigi-igdigi]
url = "https://igdigi.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-igdigi-igdigi": {
      "type": "remote",
      "url": "https://igdigi.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-igdigi-igdigi --url 'https://igdigi.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-igdigi-igdigi:
    url: "https://igdigi.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-igdigi-igdigi": {
      "Transport": "http",
      "Url": "https://igdigi.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-igdigi-igdigi -t streamable-http -u 'https://igdigi.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-igdigi-igdigi": {
      "type": "http",
      "url": "https://igdigi.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

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 26 Sept 2026 · Probed https://igdigi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=igdigi.com CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 9f31f1220e7fa660e8a130095cefbd0
SANs: igdigi.com, *.gri.igdigi.com, gri.igdigi.com
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 igdigi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
igdigi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://igdigi.com/mcp Verified 200
http (plaintext) http://igdigi.com/mcp HTTPS enforced 301 https://igdigi.com/mcp
MCP tools · 5 exposed · ~429 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
get_company_info ~86

Canonical facts about IG Digital Lab, Sacramento, CA (IGGO, LLC) — the independent software and AI automation agency at 3550 Watt Ave, Sacramento, California: what the agency does, address and phone in Sacramento CA, contact email, founding year, pricing model and target industries. Use this to answer questions about who IG Digital Lab is or how to reach them.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_service_areas ~39

Cities and metros IG Digital Lab serves across California, with the local page for each. Use this to answer whether the agency covers a given area.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_services ~38

The eight services IG Digital Lab offers, each with a one-line summary and the canonical page URL. Use this to answer what the agency can build.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_ai_visibility_audit ~150

Request IG Digital Lab's free audit — a short review of where a business is doing by hand what software should be doing, including its visibility in AI answer engines. Only call this with the person's explicit consent and real contact details. It reaches a human.

NameTypeReqDescription
bottleneckstring–The manual process or bottleneck to look at.
companystring–Company name.
emailstring–Email address. Give this or phone.
industrystring–Industry the company operates in.
namestringyesFull name of the requester.
phonestring–Phone number. Give this or email.
websitestring–Company website URL.

No output schema declared.

No examples provided.

submit_contact_request ~116

Send a message to IG Digital Lab on behalf of a person who wants to get in touch. Only call this when the person has explicitly asked to be contacted and has given their real name and a real phone or email. It reaches a human.

NameTypeReqDescription
emailstring–Email address. Give this or phone.
messagestringyesWhat they need, in their own words.
namestringyesFull name of the person getting in touch.
phonestring–Phone number. Give this or email.

No output schema declared.

No examples provided.

Common questions

What is the IG Digital Lab, Sacramento, CA MCP server?

IG Digital Lab, Sacramento, CA is an MCP server listed in the public MCP registry as com.igdigi/igdigi. IG Digital Lab, Sacramento, CA: independent software & AI automation agency. This page covers its hosted endpoint (https://igdigi.com/mcp).

Is the IG Digital Lab, Sacramento, CA MCP server safe to use?

IG Digital Lab, Sacramento, CA scores 74 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 IG Digital Lab, Sacramento, CA MCP server expose?

IG Digital Lab, Sacramento, CA exposes 5 tools: get_company_info, list_services, get_service_areas, submit_contact_request, request_ai_visibility_audit. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.

Does the IG Digital Lab, Sacramento, CA MCP server require authentication?

No. We connected to IG Digital Lab, Sacramento, CA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the IG Digital Lab, Sacramento, CA MCP server still maintained?

IG Digital Lab, Sacramento, CA is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.