TESSA Marketing & Technology
REMOTE · AIAGENT.TESSA.TECH · SCANNED SEP 20
TESSA's AI interface: services, case studies, AI-readiness audits, professional services directory.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the TESSA Marketing & Technology MCP server?
TESSA Marketing & Technology is a hosted endpoint at https://aiagent.tessa.tech/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 · aiagent.tessa.tech
claude mcp add --transport http tech-tessa-tessa-mcp-server 'https://aiagent.tessa.tech/mcp'
{
"mcpServers": {
"tech-tessa-tessa-mcp-server": {
"url": "https://aiagent.tessa.tech/mcp"
}
}
} {
"servers": {
"tech-tessa-tessa-mcp-server": {
"type": "http",
"url": "https://aiagent.tessa.tech/mcp"
}
}
} [mcp_servers.tech-tessa-tessa-mcp-server] url = "https://aiagent.tessa.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-tessa-tessa-mcp-server": {
"type": "remote",
"url": "https://aiagent.tessa.tech/mcp",
"enabled": true
}
}
} openclaw mcp add tech-tessa-tessa-mcp-server --url 'https://aiagent.tessa.tech/mcp' --transport streamable-http
mcp_servers:
tech-tessa-tessa-mcp-server:
url: "https://aiagent.tessa.tech/mcp" {
"McpServers": {
"tech-tessa-tessa-mcp-server": {
"Transport": "http",
"Url": "https://aiagent.tessa.tech/mcp"
}
}
} assistant mcp add tech-tessa-tessa-mcp-server -t streamable-http -u 'https://aiagent.tessa.tech/mcp'
{
"mcpServers": {
"tech-tessa-tessa-mcp-server": {
"type": "http",
"url": "https://aiagent.tessa.tech/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −41
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 +40
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Stability: unverified → 0.93 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 −17
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.97 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- 14 Sept 26 −23
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 +22
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → good ▲ functional
- Stability: pass → 0.93 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Sept 26 +18
- Stability: unverified → pass ▲ security
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 2026 · Probed https://aiagent.tessa.tech/mcp/ · Declared URL https://aiagent.tessa.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aiagent.tessa.tech | CN=YR1,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | RSA 2048 | SHA256-RSA | 669cb939ec7db7bfa8105880986ec60d48d |
| SANs: aiagent.tessa.tech | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aiagent.tessa.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| tessa.tech. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aiagent.tessa.tech/mcp | Redirected | 308 | /mcp/ |
| streamable-http · followed | https://aiagent.tessa.tech/mcp/ | Verified | 200 | |
| http (plaintext) | http://aiagent.tessa.tech/mcp | HTTPS enforced | 301 | https://aiagent.tessa.tech/mcp |
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 →
assess_ai_readiness ~74
Given a website URL, returns a 0-100 AI Agent Readiness score with category breakdowns (structured data, metadata quality, agent discoverability, AI-bot friendliness) and concrete recommendations. Pure deterministic check, fast, no LLM call.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
claim_listing ~118
Record a firm's intent to claim its directory listing. Pre-OAuth this does NOT automatically grant control of the listing. TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. The full self-service OAuth-2.1 claim flow lands in a follow-up plan.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_email | string | yes | – |
| claimant_name | – | – | – |
| claimant_role | – | – | – |
| firm_slug | string | yes | – |
No output schema declared.
No examples provided.
find_professional_services_firm ~98
Search the TESSA Professional Services Directory. industry: segment slug ('marketing' | 'compliance') or free-text keyword region: city or state name (case-insensitive contains) capability: keyword to match against firm descriptions and service names limit: max results
| Name | Type | Req | Description |
|---|---|---|---|
| capability | – | – | – |
| industry | – | – | – |
| limit | integer | – | – |
| region | – | – | – |
No output schema declared.
No examples provided.
get_case_studies ~62
Returns TESSA's portfolio of project results. Optional filters: industry: industry name keyword (case-insensitive contains) service_slug: filter to studies that used a given service
| Name | Type | Req | Description |
|---|---|---|---|
| industry | – | – | – |
| service_slug | – | – | – |
No output schema declared.
No examples provided.
get_firm_profile ~60
Returns the full dossier for a single firm in the directory: description, headquarters, founded year, employee band, services, locations, and directory meta (publisher, claim URL, takedown URL).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_services ~127
Returns TESSA's full service catalog (SEO, paid media, web/app development, AI agent readiness, accessibility, and more). Each service includes its live per-service A2A card URL (`agent_card`) and JSON-RPC endpoint (`a2a_endpoint`), so you can discover a service here and then talk to its dedicated A2A agent. Optional filters: category_slug: marketing | web-development | ai-experiences service_slug: filter to one specific service
| Name | Type | Req | Description |
|---|---|---|---|
| category_slug | – | – | – |
| service_slug | – | – | – |
No output schema declared.
No examples provided.
get_wcag_audit ~96
Returns the structured offering for TESSA's WCAG 2.2 AA Accessibility Audit: scope, deliverables, timeline, pricing bands (hourly + engagement range), paired service-type slugs, and the URL of TESSA's profile in the TESSA Compliance Registry. Use this when a buyer agent needs TESSA's accessibility audit offering in structured form.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_introduction ~151
Request an informational introduction — to TESSA itself, or to any directory firm if you pass target_firm_slug. TESSA logs the lead and either notifies sales@tessa.tech + kevincallen@tessa.tech (TESSA leads) or forwards a warm intro email to the firm with TESSA Cc'd (directory leads). No calendar booking — use request_strategy_session to book a meeting with TESSA.
| Name | Type | Req | Description |
|---|---|---|---|
| project_brief | – | – | – |
| prospect_email | string | yes | – |
| prospect_name | – | – | – |
| prospect_org | – | – | – |
| requested_window | – | – | – |
| target_firm_slug | – | – | – |
No output schema declared.
No examples provided.
request_quote ~168
Request a quote from a directory firm. Lighter-weight than request_introduction — explicitly framed as a budget+scope inquiry. firm_slug: directory slug for the target firm prospect_email: caller's email for the firm's reply scope_summary: one-paragraph description of the work budget_band: 'under_5k' | '5k_25k' | '25k_100k' | '100k_plus' | 'open' — or any free-text dollar figure
| Name | Type | Req | Description |
|---|---|---|---|
| budget_band | – | – | – |
| firm_slug | string | yes | – |
| prospect_email | string | yes | – |
| prospect_name | – | – | – |
| prospect_org | – | – | – |
| requested_window | – | – | – |
| scope_summary | string | yes | – |
No output schema declared.
No examples provided.
request_strategy_session ~186
Book a 30-minute strategy session with TESSA on Kevin Callen's calendar. Finds an open slot in the requested window (or the next 5 business days), creates a Google Calendar event with a Google Meet link, and emails the prospect the invite. If no slot is available, captures the lead and Kevin follows up manually. TESSA-only tool — directory firms use request_introduction instead. requested_window accepts ISO 8601 ranges ('2026-04-30T13:00/2026-04-30T17:00'), single dates ('2026-04-30'), or English ('tomorrow', 'next week').
| Name | Type | Req | Description |
|---|---|---|---|
| project_brief | – | – | – |
| prospect_email | string | yes | – |
| prospect_name | – | – | – |
| prospect_org | – | – | – |
| requested_window | – | – | – |
No output schema declared.
No examples provided.
What is the TESSA Marketing & Technology MCP server?
TESSA Marketing & Technology is an MCP server listed in the public MCP registry as tech.tessa/tessa-mcp-server. TESSA's AI interface: services, case studies, AI-readiness audits, professional services directory. This page covers its hosted endpoint (https://aiagent.tessa.tech/mcp).
Is the TESSA Marketing & Technology MCP server safe to use?
TESSA Marketing & Technology scores 33 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 TESSA Marketing & Technology MCP server expose?
TESSA Marketing & Technology exposes 10 tools: get_services, get_case_studies, assess_ai_readiness, find_professional_services_firm, get_firm_profile, and 5 more. Their descriptions and schemas cost roughly 1,140 tokens of context every time the server is loaded.
Does the TESSA Marketing & Technology MCP server require authentication?
No. We connected to TESSA Marketing & Technology without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TESSA Marketing & Technology MCP server still maintained?
TESSA Marketing & Technology is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.