MCP servers › com.meowapps › ai-engine

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

com.meowapps/ai-engine

AI Engine for WordPress — the publisher's title

by meowapps.com · domain (the registry's namespace rule)Website ↗

Free MCP server for WordPress: Claude and ChatGPT connect with OAuth. No account, cap or API key. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-27version 3.8.8streamable HTTP30 tools

Summary

com.meowapps/ai-engine is a remote MCP server listed in the official MCP registry at version 3.8.8, under the namespace of the domain meowapps.com. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 0 resources and 4 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 30
Last tested: 2026-10-27

Tool list size

6,389 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (30 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (connect.meowapps.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (3.8.8).

Add to your client

Observed fact

This server accepted a session without any credential and lists 15 tools whose name or declaration suggests they change data (wp_create_post, wp_update_post, wp_alter_post, wp_write_blocks, wp_delete_post and 10 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-27.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-27

Mode

read-only (no tool calls)

Latest version

3.8.8, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)

First listed version

2026-10-26 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-26 to 2026-10-27; 2 in the 90 days before the 2026-10-27 snapshot.

Most recent 2 versions

3.8.8 · 2026-10-27
3.8.7 · 2026-10-26

(versions still listed in the registry only)

Registry data

snapshot 2026-10-27

Package and repository

checked 2026-10-27

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 3.8.7 (published 2026-10-26) → 3.8.8 (published 2026-10-27), between the registry lists of 2026-10-26 and 2026-10-27.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27; release notes from the GitHub Releases API, checked 2026-10-27.

What it is

What does this server offer?

Observed inventory

30tools

0resources

4prompts

None of its 30 tools are described as changing anything. For 30 the reading was uncertain, so no mark is shown.

wp_get_posts
“List posts, pages or another post type, newest first.”
Publisher declares: read-only yes · destructive no · open-world no
11 inputs
- post_typestring
- post_statusstring
- searchstring
- authorinteger“Filter by author user ID.”
- author_namestring“Filter by author user slug (nicename).”
- author__not_inarray“Exclude posts by these author user IDs.”
- afterstring
- beforestring
- limitinteger
- offsetinteger
- pagedinteger
wp_get_post
“Get one post or page by ID: title, content, status, dates and permalink.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- IDintegerrequired
- content_formatstring“full (default) returns raw content; prose strips block-attribute JSON, keeping prose, headings and block markers.”
wp_get_post_snapshot
“Get everything about one post by ID: all fields, custom fields, terms, featured image and author.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs, 1 required
- IDintegerrequired“Post ID”
- includearray“Optional: fields to include (default: all).”
- excludearray“Optional: fields to exclude from post data.”
- content_formatstring“full (default) returns raw content; prose strips block-attribute JSON (huge gallery blobs), keeping prose and block markers.”
wp_count_posts
“Count posts by status (published, draft, scheduled, pending, private, trash) for one post type.”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- post_typestring
wp_get_post_types
“List the public post types on the site with their key and label, such as post, page or product.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
wp_get_post_meta
“Get the custom fields of a post by ID.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- IDintegerrequired
- keystring
wp_get_comments
“List comments with their post, author, content, date and approval status.”
Publisher declares: read-only yes · destructive no · open-world no
9 inputs
- post_idinteger
- statusstring
- typestring“Filter by comment type, e.g.”
- searchstring
- user_idinteger“Filter by the registered user ID of the commenter.”
- author_emailstring“Filter by the commenter email address.”
- limitinteger
- offsetinteger
- pagedinteger
wp_get_taxonomies
“List the taxonomies available for a post type, such as categories and tags.”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- post_typestring
wp_get_terms
“List the terms of a taxonomy (for example every category), optionally filtered by search text or parent term.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs, 1 required
- taxonomystringrequired
- searchstring
- parentinteger
- limitinteger
wp_count_terms
“Count the terms in a taxonomy.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- taxonomystringrequired
wp_get_post_terms
“List the terms attached to a post, optionally for one taxonomy only.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- IDintegerrequired
- taxonomystring
wp_get_media
“List items in the Media Library with their ID, title and URL.”
Publisher declares: read-only yes · destructive no · open-world no
6 inputs
- searchstring
- authorinteger“Filter by uploader user ID.”
- author_namestring“Filter by uploader user slug (nicename).”
- afterstring
- beforestring
- limitinteger

Show 18 more tools

wp_count_media
“Count the items in the Media Library, optionally within a date range.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- afterstring
- beforestring
wp_list_block_patterns
“List the block patterns available on the site (ready-made layouts from WordPress, the theme and plugins), with name, title, categories and description.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs
- searchstring“Case-insensitive filter on title, name, description, and keywords.”
- categorystring“Pattern category slug, e.g.”
- include_contentboolean“Include each match's raw block markup (default false; can be large).”
- limitinteger“Max patterns to return (default 50, max 500).”
wp_create_post
“Create a post, page or item of another post type.”
Publisher declares: read-only no · destructive no · open-world yes
7 inputs, 1 required
- post_titlestringrequired
- post_contentstring
- post_excerptstring
- post_statusstring
- post_typestring
- post_namestring
- meta_inputobject“Custom fields as key/value pairs.”
wp_update_post
“Update an existing post by ID: title, content, excerpt, status, slug, date or custom fields.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs, 1 required
- IDintegerrequired“The ID of the post to update.”
- fieldsobject
- meta_inputobject“Custom fields as key/value pairs.”
- schedule_forstring“Schedule post for future publication.”
wp_alter_post
“Find and replace text inside one field of a post (for example its content), without sending the whole content again.”
Publisher declares: read-only no · destructive yes · open-world yes
6 inputs, 4 required
- IDintegerrequired“Post ID.”
- fieldstringrequired“Field to modify: post_content, post_excerpt, or post_title.”
- searchstringrequired“Text to search for, or (with regex=true) a bare PCRE pattern without delimiters, e.g.”
- replacestringrequired“Replacement text.”
- regexboolean“Treat search as a regex pattern (default: false).”
- flagsstring“Optional PCRE modifier letters applied in regex mode, e.g.”
wp_write_blocks
“Write block editor content to an existing post from a list of block specs.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
- IDintegerrequired“Target post/page ID (create it first with wp_create_post).”
- blocksarrayrequired“Ordered array of block specs.”
- modestring“replace (default) overwrites post_content; append/prepend add the blocks to the existing content.”
wp_delete_post
“Move a post, page or item of another post type to the trash by ID.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
- IDintegerrequired
wp_set_featured_image
“Set the featured image of a post to a Media Library item, or remove it when media_id is empty.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 1 required
- post_idintegerrequired
- media_idinteger
wp_create_term
“Create a term in a taxonomy, such as a new category or tag, with an optional slug, description and parent.”
Publisher declares: read-only no · destructive no · open-world no
5 inputs, 2 required
- taxonomystringrequired
- term_namestringrequired
- slugstring
- descriptionstring
- parentinteger
wp_update_term
“Update the name, slug, description or parent of an existing term.”
Publisher declares: read-only no · destructive yes · open-world no
6 inputs, 2 required
- term_idintegerrequired
- taxonomystringrequired
- namestring
- slugstring
- descriptionstring
- parentinteger
wp_add_post_terms
“Attach terms to a post.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 2 required
- IDintegerrequired
- taxonomystring
- termsarrayrequired
- appendboolean
wp_upload_media
“Add a file to the Media Library, either from a public URL that WordPress downloads or from base64 content with a filename.”
Publisher declares: read-only no · destructive no · open-world yes
6 inputs
- urlstring“URL to download the file from.”
- base64string“Base64-encoded file content.”
- filenamestring“Filename with extension (e.g.”
- titlestring
- descriptionstring
- altstring
wp_update_media
“Update the title, caption, description or alt text of a Media Library item.”
Publisher declares: read-only no · destructive yes · open-world no
5 inputs, 1 required
- IDintegerrequired
- titlestring
- captionstring
- descriptionstring
- altstring
wp_create_comment
“Add a comment to a post.”
Publisher declares: read-only no · destructive no · open-world yes
6 inputs, 2 required
- post_idintegerrequired
- comment_contentstringrequired
- comment_authorstring
- comment_author_emailstring
- comment_author_urlstring
- comment_approvedstring
wp_update_comment
“Update a comment by ID: its content or its approval status (approve, hold or mark as spam).”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 1 required
- comment_IDintegerrequired
- fieldsobject
wp_create_note
“Add an editor note to a block of a post (WordPress 6.9 or later), as shown in the editor's Notes panel.”
Publisher declares: read-only no · destructive no · open-world no
5 inputs, 1 required
- post_idinteger“The post to annotate.”
- contentstringrequired“The note text.”
- anchor_textstring“A short exact snippet of text from the block the note is about.”
- block_indexinteger“Alternative to anchor_text: 0-based position among the top-level blocks.”
- parent_idinteger“Reply to this note instead of starting a new thread.”
wp_update_note
“Edit the text of an editor note, or mark its thread as resolved or reopen it.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 1 required
- note_idintegerrequired
- contentstring“New text for the note.”
- statusstring“Resolve or reopen the thread (top-level notes only).”
wp_get_site_info
“Get the site's name, tagline, address and time zone.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 35% of 114
Tools with a description: 100% of 30
Typical description length: 150 characters

The tool set

Counted from the listing

Tools: 30
Size of the list: about 4,823 tokens for an agent to load (characters ÷ 4)
Naming: 30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://connect.meowapps.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ai-engine": {
      "url": "https://connect.meowapps.com/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "ai-engine": {
      "type": "http",
      "url": "https://connect.meowapps.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"ai-engine","type":"http","url":"https://connect.meowapps.com/mcp"}'

Claude Code

claude mcp add --transport http ai-engine https://connect.meowapps.com/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "ai-engine": {
      "type": "streamableHttp",
      "url": "https://connect.meowapps.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "ai-engine": {
      "httpUrl": "https://connect.meowapps.com/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.ai-engine]
url = "https://connect.meowapps.com/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "ai-engine": {
      "url": "https://connect.meowapps.com/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://connect.meowapps.com/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint connect.meowapps.com/mcp	Session opened	matches	our test · 2026-10-27
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-27

Tool list changes

Our reads compared · no tool called

Hosted endpoint connect.meowapps.com/mcp

No change in the tool list across 2 reads (2026-10-26 to 2026-10-27; versions 3.8.7 to 3.8.8).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-27 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.meowapps/ai-engine

Answered from the data above

Who publishes com.meowapps/ai-engine?

The registry ties the namespace com.meowapps to the domain meowapps.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.meowapps/ai-engine need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.meowapps/ai-engine been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
483 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 30 tools, 0 resources, 4 prompts.
1,943 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-27; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-27

MCP capability

prompts, tools

our test · 2026-10-27

Transport

streamable HTTP

registry · 2026-10-27

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-27

Lifecycle status

active

registry · 2026-10-27

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.meowapps/ai-engine: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/com.meowapps/ai-engine

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.meowapps/ai-engine)](https://protocolprobe.com/mcp/servers/com.meowapps/ai-engine)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology